-
Notifications
You must be signed in to change notification settings - Fork 292
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
Compatibility with Python-3.13 #640
Comments
which is being removed in Python 3.13, by backporting python/cpython@407c3af Partial fix for PythonCharmers#640 . Also: - Backport small fixes from upstream `email` library module - Remove unused imports
I've opened #644 to get rid of |
Hello, is this library still under active development? Unfortunately I'm considering to remove it from my project due to lack of python 3.13 support and search for a replacement. |
Hi @MaxXor , No, the library is no longer in active development. Please see the note here about the project's status. Python 3.13 removes the 2to3 machinery which The need for the |
I see, thanks for the insights @edschofield. I've been using this library in a smart meter project for a long time. Unfortunately I have to support some legacy systems as well. 😢 I think I'll stick with python 3.12 for the time being until I can drop python 2.7 support altogether in the near future. |
Hi all.
Please, if reasonable for you, render
python-future
compatible with newer Python-3.13uu
andlib2to3
modules are no longer available and some tests fail:The text was updated successfully, but these errors were encountered: