-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python-3 support #8
Comments
Yes, we discussed this at the meeting and put it as a high development priority. I directed everyone to the PETSc PR with the Python-3 upgrade. Our only real stumbling block here is Pyre. |
I'd be happy to help with |
Needs to be coordinated with updating Python 3 for Pythia, nemesis, and PyLith. See geodynamics/pylith#31, geodynamics/nemesis#2, geodynamics/pythia#4. |
Python2 EOL is fast approaching and the present codebase is python2-only. futurize is a useful tool for converting a python2 codebase to Python3.
I have some experience using futurize, but I can't currently run the test suite. My system has the default /usr/bin/python as python3. While the autoconf script finds
python2
correctly, it seems to be runningpytest
rather thanpytest2
, thus tests fail to import the python2 module. I'm not sure what is intended here and haven't dug in to debug yet.The text was updated successfully, but these errors were encountered: