<div dir="ltr">Hi David,<div><br></div><div>The plan is to have code that is compatible with both Python 2 and Python 3. In terms of a post-transition period, I don't think we've though about a timeline for when we make the switch to Python 3 only, so it's open for discussion. I'm trying to get things running on Python 3 first!</div><div><br></div><div>I don't know if a specific month in 2020 has been set yet for the official end of Python 2, so the period of Python 2/3 compatibility can probably go into 2020. And since Python 2.0 source code is still available, I would guess that Python 2.7 source code will be available for a while in case we need it past the official end of Python 2.</div><div><br clear="all"><div><div dir="ltr" class="m_-6444212256875459417gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><div>--</div><div><span style="font-size:12.8000001907349px">Billy K. Poon</span><br></div></div><div>Research Scientist, Molecular Biophysics and Integrated Bioimaging</div><div>Lawrence Berkeley National Laboratory</div><div>1 Cyclotron Road, M/S 33R0345</div><div>Berkeley, CA 94720</div><div>Tel: (510) 486-5709</div><div>Fax: (510) 486-5909</div><div>Web: <a href="https://phenix-online.org" target="_blank">https://phenix-online.org</a></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 1, 2018 at 5:07 AM David Waterman <<a href="mailto:dgwaterman@gmail.com" target="_blank">dgwaterman@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi folks,<div><br></div><div>It's great to see the momentum building behind the project to migrate to Python 3. From the <a href="https://github.com/cctbx/cctbx_project/wiki/Python-3-roadmap" target="_blank">roadmap</a>, there is clearly still some way to go, but current activity makes me wonder if the proposed deadline of complete migration by 2020 might be beaten easily. What is not clear from the roadmap is whether there are any plans for a post-transition grace period, in which we have switched from writing forwards compatible Python 2 code to writing backwards compatible Python 3 code. Has this been thought about? Or will it be the case that the first commit of Py3-only code seals the deal?</div><div><br></div><div>I ask because CCP4 has to support a large number of Python projects and these have not all considered the Python 3 switch nearly as seriously as cctbx yet. What I would like to request is a reasonable period of backwards compatibility is ensured to allow other CCP4 projects to catch up, and that this protected period is enshrined within the roadmap or developer guidelines. What do you think?</div><div><br></div><div>Best wishes</div><div><div><div dir="ltr" class="m_-6444212256875459417m_-7761503644696846062gmail_signature" data-smartmail="gmail_signature">-- David<br></div></div></div></div>
_______________________________________________<br>
cctbxbb mailing list<br>
<a href="mailto:cctbxbb@phenix-online.org" target="_blank">cctbxbb@phenix-online.org</a><br>
<a href="http://phenix-online.org/mailman/listinfo/cctbxbb" rel="noreferrer" target="_blank">http://phenix-online.org/mailman/listinfo/cctbxbb</a><br>
</blockquote></div>