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

[Jan M. Simons]

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
> 
>