-
Notifications
You must be signed in to change notification settings - Fork 33
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
this package neved needed "future" #283
Conversation
|
Are you sure? The code does not compile for python 2.7 without it. |
I m pretty sure. I got "future" removed from Debian. The |
“as long as py2.7 compatibility is wanted”. Py2.7 compatibility is wanted for this library. And I do not see why you are mentioning Debian. This is Python. |
I read again the documentation, and future IS required.
If you still think it is a mistake, please provide more explanation and references. In the meantime, I am closing this PR. |
Future is a failed project. The winner was Six. Future own documentation read more like propaganda. Here is the documentation you want: https://docs.python.org/3/library/__future__.html |
What you provided is about |
The build failure is unrelated. This project neihlther need future nor six
but relies in the standard library
Le lun. 14 oct. 2024, 21:36, Sebastien Andrivet ***@***.***>
a écrit :
… What you provided is about *future*. What I am talking is about the
future python package. “Future is a failed project. The winner was Six.”.
This is your point of view. I will not change the library based on a point
of view. The library needs the future package to be compatible with python
2.7. If. remove the package, the library does not work with python 2.7. I
will not replace it with six because I do not see any reason to do so.
—
Reply to this email directly, view it on GitHub
<#283 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB47WUHT3YDWRD3DZ6BTD3LZ3QMKRAVCNFSM6AAAAABP4VPZ6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJSGA3DKNJTGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
You make affirmations without providing any evidences to support them. So let’s stop this discussion that goes nowhere. |
I see https://askubuntu.com/questions/697226/importerror-no-module-named-builtins
|
Hi,
__future__
andfuture
are not the same thing.__future__
is included in the standard library.