Fwd: Target platform with conda
Hello all Looking at the commits relating to conda, what are the target platforms now? Looks like 3.7 is valid? I’m asking as it would be good to know what language features we can adopt without causing incompatible code problems. We’ve clearly nearly got up to date on Python 3 now... Do we have guidelines somewhere? Thanks Graeme -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
It makes sense for libraries to support as many python versions as possible, since it's unknown how these libraries will be used. Example: https://anaconda.org/anaconda/numpy/files. Numpy has a conda package for each of python 3.6, 3.7 and 3.8. Or https://pypi.org/project/numpy/#files, where python 3.5-3.8 wheels are available. Cctbx is a library, so I think python 3.6 should be the minimum supported version of python 3, until its end of life in Dec 2021. On Tue, Nov 5, 2019 at 10:44 PM Winter, Graeme (DLSLtd,RAL,LSCI) < [email protected]> wrote:
Hello all
Looking at the commits relating to conda, what are the target platforms now? Looks like 3.7 is valid?
I’m asking as it would be good to know what language features we can adopt without causing incompatible code problems. We’ve clearly nearly got up to date on Python 3 now...
Do we have guidelines somewhere?
Thanks Graeme -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb
(Also, note that we'll need to preserve py2 backwards compatibility while
other projects finish their migrations)
On Wed, Nov 6, 2019 at 10:20 AM Aaron Brewster
It makes sense for libraries to support as many python versions as possible, since it's unknown how these libraries will be used. Example: https://anaconda.org/anaconda/numpy/files. Numpy has a conda package for each of python 3.6, 3.7 and 3.8. Or https://pypi.org/project/numpy/#files, where python 3.5-3.8 wheels are available. Cctbx is a library, so I think python 3.6 should be the minimum supported version of python 3, until its end of life in Dec 2021.
On Tue, Nov 5, 2019 at 10:44 PM Winter, Graeme (DLSLtd,RAL,LSCI) < [email protected]> wrote:
Hello all
Looking at the commits relating to conda, what are the target platforms now? Looks like 3.7 is valid?
I’m asking as it would be good to know what language features we can adopt without causing incompatible code problems. We’ve clearly nearly got up to date on Python 3 now...
Do we have guidelines somewhere?
Thanks Graeme -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb
Do we have a time-frame for this? Clearly projects which use cctbx but are not part of it are not constrained by this, but I can imagine new language features being useful inside cctbx too.
Thanks Graeme
On 6 Nov 2019, at 23:18, Aaron Brewster
participants (2)
-
Aaron Brewster -
Winter, Graeme (DLSLtd,RAL,LSCI)