Skip to content
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

Closed
jedbrown opened this issue Jun 16, 2019 · 3 comments · Fixed by #45
Closed

Python-3 support #8

jedbrown opened this issue Jun 16, 2019 · 3 comments · Fixed by #45

Comments

@jedbrown
Copy link
Contributor

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 running pytest rather than pytest2, thus tests fail to import the python2 module. I'm not sure what is intended here and haven't dug in to debug yet.

@knepley
Copy link
Contributor

knepley commented Jun 17, 2019

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.

@jedbrown
Copy link
Contributor Author

I'd be happy to help with futurize, but these packages aren't familiar to me and I'd need a working test suite. (I suppose it would probably work if I ran inside an older container.)

@baagaard-usgs
Copy link
Contributor

Needs to be coordinated with updating Python 3 for Pythia, nemesis, and PyLith. See geodynamics/pylith#31, geodynamics/nemesis#2, geodynamics/pythia#4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants