-
Notifications
You must be signed in to change notification settings - Fork 15.4k
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
pip construes "3.0.0-alpha-1" as later than "3.0.0a3" #855
Comments
When I look at https://pypi.python.org/pypi/protobuf today I don't see a 3.0.0-alpha-1 package, so it seems to me that this issue is likely resolved. Please close if you agree? |
This is possible now that protocolbuffers/protobuf#855 is fixed (or at least appears to be fixed).
Yes, we removed (hide) the 3.0.0-alpha-1 package due to the inconsistent naming. |
Just as an FYI: We got bitten by this issue in the wild. Apparently, we've hit a specific combination of software versions in our Travis CI tests where the hidden alpha-1 release is not ignored. Output from the pip -v command which installs gRPC Python:
This is supposedly with pip 1.1. Full log: https://travis-ci.org/youtube/vitess/builds/113311581 However, I could not reproduce the issue locally with a pip version 1.1. On other machines, it always ignores the alpha-1 version:
This is just an FYI. I don't understand what's wrong there and gave up debugging it. Instead, I'll work-around the issue by explicitly pinning our gRPC Python copy to protobuf 3.0.0a3. |
Trivially reproducible for me; let me know if you have problems:
I currently can't write any dependencies as
protobuf>=3.0.0a3
and count on them getting the latest version of protobuf from PyPI.@haberman: I suspect that the right thing to do here is remove the 3.0.0-alpha-1 package, even if doing so breaks some folks - "alpha" does mean "occasional hardship".
The text was updated successfully, but these errors were encountered: