You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently had an issue where my production build stopped working because it picked up a pre-release version of protobuf. pex protobuf will pick up version 3.2.0rc2 right now, while a pip install will pick up 3.1.0.post1. I didn't expect this to happen and there doesn't appear to be a way to change the behavior.
The text was updated successfully, but these errors were encountered:
pip seems to be following PEP 440 and defining stable releases to exclude pre-releases (those including a, b, or rc in the version identifier) and developmental releases (those with dev followed by a number at the end).
I recently had an issue where my production build stopped working because it picked up a pre-release version of protobuf.
pex protobuf
will pick up version3.2.0rc2
right now, while a pip install will pick up3.1.0.post1
. I didn't expect this to happen and there doesn't appear to be a way to change the behavior.The text was updated successfully, but these errors were encountered: