-
-
Notifications
You must be signed in to change notification settings - Fork 531
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 the --pre pip option by default #193
Comments
Original comment by @hpk42 tox-1.9 does not use |
Original comment by @cjw296 I'll second the voices in Ned's posting: please remove --pre, it creates unpleasant breakage... |
Original comment by @dstufft Sort of? |
Original comment by @hpk42 if i do |
Original comment by @dstufft FWIW I don't think pip ever mandated that you have |
This can break some builds
I looked at the Changelog for when this change was introduced, and apparently pip would refuse to install the exactly specified prerelease dependencies unless the
--pre
flag was suppliedThis is understandable, but apparently it's not the case anymore, since if you run
pip install coverage==4.0a1
it will install the package without making a fussI don't know when pip changed its behavior, but it'd be nice to take it into account now
The text was updated successfully, but these errors were encountered: