-
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
Importing imp in standard_library raises a PendingDeprecationWarning #246
Comments
The python-future library is causing a warning about the imp module being deprecated. See PythonCharmers/python-future#246 This commit suppresses the warning.
Any hope to get this fixed? Still happening after 3 years. |
Assuming no one has plans to fix this? Currently tracking the source of a Editing in an idea here, but what's the potential cost of importing I'd work out a solution myself, but I'm not working with |
Greetings again from the Is python-future dead? Once Python 3.12 releases, this project will be left in a forever broken state if not updated. EDIT 2: Updating my previous edit, it would seem the imp module deprecation is still present in 0.18.3. Will this ever be fixed? |
The
Python 3.12 will be in beta in two weeks, and set for release on 2023-10-02 and this library is one of the top 5,000 most-downloaded from PyPI. Please could you upgrade to use |
For people googling, in python 3.12, importing
In my case, I resolved the error by replacing those imports that need
|
The
imp
package is pending deprecation in favor ofimportlib
as of Python 3.4.The recommended alternative is described here.
The text was updated successfully, but these errors were encountered: