-
Notifications
You must be signed in to change notification settings - Fork 291
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.12 removes imp module #625
Comments
4 tasks
Tried my hand at a PR but I can't dip into another codebase right now and I'm unsure of the state of some of the tests. |
Thank you for submitting GH-626. We are also running into this over at mqttwarn. |
1 task
1 task
This was referenced Oct 28, 2023
rcrdnalor
added a commit
to rcrdnalor/mythtv
that referenced
this issue
Jan 8, 2024
Python 3.12 removes the imp module but python-future v0.18.3 uses it, see PythonCharmers/python-future#625 Since 4b5eac8, python-future is not needed anymore.
6 tasks
rcrdnalor
added a commit
to MythTV/mythtv
that referenced
this issue
Jan 8, 2024
Python 3.12 removes the imp module but python-future v0.18.3 uses it, see PythonCharmers/python-future#625 Since 4b5eac8, python-future is not needed anymore.
Any chance for a real fix and not just a workaround? I've got a project that uses this as a dependency 2 levels down, causing me to be python 3.12 incompatible. |
Merged
@liquidsec Have a look at #632 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Future relies on the imp module in standard_library, used for things like
from future.standard_library import hooks
. In Python 3.12, the module has been completely removed. Future needs to switch to use importlib.Workaround
If your code is like this
You can rewrite it using the try-except form in the Cheat Sheet.
The text was updated successfully, but these errors were encountered: