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.

Sign up for GitHub

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

Jump to bottom

future.standard_library breaking python 3.12 compatibility #997

Open
boatmorrow opened this issue Jan 25, 2024 · 1 comment · May be fixed by #1023
Open

future.standard_library breaking python 3.12 compatibility #997

boatmorrow opened this issue Jan 25, 2024 · 1 comment · May be fixed by #1023
Labels
bug Py3k

Comments

@boatmorrow
Copy link

future.standard_library imports the imp module which is gone in python 3.12. So, future.standard_library is not really python 3.12 compatible.

issue tracker

This means fipy breaks in python 3.12 at the import of the entire future.standard_library. I'm thinking a work around could be, to be more selective about what parts of future are imported?
@guyer guyer linked a pull request Feb 22, 2024 that will close this issue
Draft
@guyer
Copy link
Member

guyer commented Feb 22, 2024

I'm impressed you got FiPy to install with Python 3.12 at all. I've fixed this particular issue on #1023. That won't be merged to master until I can expunge Python 2.7 (RealSoonNow (tm)) (versioneer.py cannot be compatible with Python 2.7 and Python 3.12).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Py3k
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[WIP] Make compatible with Python 3.12 usnistgov/fipy
2 participants
@guyer @boatmorrow