[cctbxbb] Is there a schedule for the python3 migration or can cctbx.python already be built to be/use a python3 interpreter?

[Nicholas Devenish]

> can't imagine the python 3.7 non-conda build is very widely used at this
point.

This should read:
     I can't imagine the python *2*.7 non-conda build is very widely used
at this point.

obviously. My brain has obviously forgotten about the existence of the
number 2 when talking about python versions.

Nick

On Fri, Jul 9, 2021 at 12:44 PM Nicholas Devenish <ndevenish at gmail.com>
wrote:

> Hi Jan,
>
> Not an expert on cctbx bootstrap - dials uses it's own. But I think
> you need to explicitly pass "--python 37", and possibly "--use_conda"
> to the cctbx bootstrap.py; I don't know if the non-conda bootstrap was
> ever updated to use python 3. I can't imagine the python 3.7 non-conda
> build is very widely used at this point.
>
> To slightly elaborate on what Graeme said about DIALS support - for
> DIALS/dxtbx we do support 3.6+, but will be dropping 3.6 for 3.7+
> after the next release (mid-august), as we are now following the numpy
> deprecation schedule:
> https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table
>
> Nick
>
> On Fri, Jul 9, 2021 at 12:30 PM Jan M. Simons <marten at ifk.rwth-aachen.de>
> wrote:
> >
> > Am 09.07.21 um 13:16 schrieb Winter, Graeme (DLSLtd,RAL,LSCI):
> > > With DIALS we use python3 exclusively - have done so for a long while
> - everything we use from cctbx seems largely OK with this
> > >
> > > Python2 is dead to me, and many other dials devs
> >
> > Oh, that's great to hear, I really hope to have everything Python3.6+
> > soon as well.
> >
> > Still bootstrap.py seems to default to building a python 2.7.18
> > interpreter? Is this just for legacy backwards compatibility?
> >
> > All the best
> > Jan
> >
> >
> > >
> > > All the best Graeme
> > >
> > >> On 9 Jul 2021, at 11:49, Jan M. Simons <marten at ifk.rwth-aachen.de>
> wrote:
> > >>
> > >> Cheers,
> > >>
> > >> I'm getting more and more concerned with the state of cctbx and the
> > >> impending removal of python2 from quite a lot of major linux
> > >> distributions in the near future.
> > >>
> > >> So far I have not managed to find documentation on how to build the
> > >> cctbx to then use a python3 interpreter for the cctbx.python script,
> but
> > >> I would really like to have this, as I'd have to check/port my code
> > >> that's using cctbx modules (mostly smtbx and xrax) to python3 as well,
> > >> so that it does not get obsoleted.
> > >>
> > >> So is it possible to build cctbx as a python3 module by now and if so
> > >> how would one be able to do this?
> > >>
> > >> Thanks for your support
> > >> Jan
> > >> _______________________________________________
> > >> cctbxbb mailing list
> > >> cctbxbb at phenix-online.org
> > >> http://phenix-online.org/mailman/listinfo/cctbxbb
> > >
> > >
> >
> > _______________________________________________
> > cctbxbb mailing list
> > cctbxbb at phenix-online.org
> > http://phenix-online.org/mailman/listinfo/cctbxbb
>
> On Fri, Jul 9, 2021 at 12:40 PM Winter, Graeme (DLSLtd,RAL,LSCI)
> <Graeme.Winter at diamond.ac.uk> wrote:
> >
> > Dials has a custom bootstrap which gives you a recent 3 build. I forget
> if it’s 3.9 or some other. But it’s certainly up to date and supported.
> >
> > We base our build environment on conda rather than building everything
> locally which really speeds things up
> >
> > All the best Graeme
> >
> > > On 9 Jul 2021, at 12:30, Jan M. Simons <marten at ifk.rwth-aachen.de>
> wrote:
> > >
> > > Am 09.07.21 um 13:16 schrieb Winter, Graeme (DLSLtd,RAL,LSCI):
> > >> With DIALS we use python3 exclusively - have done so for a long while
> - everything we use from cctbx seems largely OK with this
> > >>
> > >> Python2 is dead to me, and many other dials devs
> > >
> > > Oh, that's great to hear, I really hope to have everything Python3.6+
> > > soon as well.
> > >
> > > Still bootstrap.py seems to default to building a python 2.7.18
> > > interpreter? Is this just for legacy backwards compatibility?
> > >
> > > All the best
> > > Jan
> > >
> > >
> > >>
> > >> All the best Graeme
> > >>
> > >>>> On 9 Jul 2021, at 11:49, Jan M. Simons <marten at ifk.rwth-aachen.de>
> wrote:
> > >>>
> > >>> Cheers,
> > >>>
> > >>> I'm getting more and more concerned with the state of cctbx and the
> > >>> impending removal of python2 from quite a lot of major linux
> > >>> distributions in the near future.
> > >>>
> > >>> So far I have not managed to find documentation on how to build the
> > >>> cctbx to then use a python3 interpreter for the cctbx.python script,
> but
> > >>> I would really like to have this, as I'd have to check/port my code
> > >>> that's using cctbx modules (mostly smtbx and xrax) to python3 as
> well,
> > >>> so that it does not get obsoleted.
> > >>>
> > >>> So is it possible to build cctbx as a python3 module by now and if so
> > >>> how would one be able to do this?
> > >>>
> > >>> Thanks for your support
> > >>> Jan
> > >>> _______________________________________________
> > >>> cctbxbb mailing list
> > >>> cctbxbb at phenix-online.org
> > >>> http://phenix-online.org/mailman/listinfo/cctbxbb
> > >>
> > >>
> > >
> > > _______________________________________________
> > > cctbxbb mailing list
> > > cctbxbb at phenix-online.org
> > > http://phenix-online.org/mailman/listinfo/cctbxbb
> >
> > --
> > 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
> > cctbxbb at phenix-online.org
> > http://phenix-online.org/mailman/listinfo/cctbxbb
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://phenix-online.org/pipermail/cctbxbb/attachments/20210709/e2244bff/attachment.htm>