You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WIP: Decided to use the future package. Current work is in py3_future branch. Current working assumption is that we can write mostly-clean python 3 code if we include this at the top of each file:
from __future__ importprint_function, unicode_literals, absolute_import, divisionfromfutureimportstandard_librarystandard_library.install_aliases()
fromfuture.builtinsimport*
String handling, however, will require much more care than with pure python 2. This branch includes a substantial file handling refactor to address py3's new str and bytes types. The various job running APIs (subprocess, CCC, docker) will also need more explicit codecs.
Current status: can now explicitly request an interpreter when starting a python job. Tests are running successfully in both languages, including calls from python 2 to 3 and vice versa.
Story: PyCCC supports python 2 and 3 with a single source branch.
We'll also be porting
nbmolviz
andmoldesign
, so we need to document:The text was updated successfully, but these errors were encountered: