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

Remove dependency on future library #38

Open
tzok opened this issue Jan 13, 2025 · 1 comment · May be fixed by #39
Open

Remove dependency on future library #38

tzok opened this issue Jan 13, 2025 · 1 comment · May be fixed by #39

Comments

@tzok
Copy link

tzok commented Jan 13, 2025

This library continues to rely on future, which is unnecessary for actively developed code using Python 3. The latest PyPI build of this package supports Python 3.6 as the minimum version, justifying the removal of future. With Python 3.13, I cannot use your library due to issues installing future.

WARNING: python-future package is not compatible with Python 3.13

The python-future project was created in 2013 to attempt to save Python from the schism of version incompatibility that was threatening to tear apart the language (as Perl 6 contributed to the death of Perl).

That time is now past. Thanks to a huge porting effort across the Python community, Python 3 eventually thrived. Python 2 reached its end of life in 2020 and the python-future package should no longer be necessary. Use it to help with porting legacy code to Python 3 but don’t depend on it for new code.

If you use packages that depend on it, please contact maintainers and/or upstream of these packages and try to work out whether this dependency is really needed.

@tzok tzok linked a pull request Jan 20, 2025 that will close this issue
@piehld
Copy link
Collaborator

piehld commented Jan 21, 2025

Thanks for reporting and the PR, @tzok! We will need some time to discuss this internally, as this may have implications for other users of this package as well as other software that makes use of this. But in general we do agree that moving things forward is the appropriate plan. We just want to be cautious in how we go about this.

FYI @epeisach

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.

2 participants