Prerelease upgrade for the exact same series should not require --pre flag #1585

Closed
techtonik opened this Issue Feb 21, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@techtonik
Contributor

techtonik commented Feb 21, 2014

Going from 1.0a1 to 1.0a2 should not require --pre flag.

@dstufft

This comment has been minimized.

Show comment
Hide comment
@dstufft

dstufft Mar 28, 2014

Member

I have mixed feelings about this. Thoughts @pypa/pip-developers ?

Member

dstufft commented Mar 28, 2014

I have mixed feelings about this. Thoughts @pypa/pip-developers ?

@pfmoore

This comment has been minimized.

Show comment
Hide comment
@pfmoore

pfmoore Mar 28, 2014

Member

I can see the logic, but I'm nervous about it becoming hard to document clearly when you do and don't need --pre. Presumably, for example, 1.0a1 -> 1.1a2 should still need --pre. What about dev releases (or dev releases of pre releases)? I don't even know what --pre does with dev at the moment.

Member

pfmoore commented Mar 28, 2014

I can see the logic, but I'm nervous about it becoming hard to document clearly when you do and don't need --pre. Presumably, for example, 1.0a1 -> 1.1a2 should still need --pre. What about dev releases (or dev releases of pre releases)? I don't even know what --pre does with dev at the moment.

@dstufft

This comment has been minimized.

Show comment
Hide comment
@dstufft

dstufft Sep 11, 2014

Member

So I'm going to close this. I can see the logic behind it but ultimately I think it's going to end up with us becoming too clever and the rules for when and when a prerelease version is installed becoming hard to explain.

Member

dstufft commented Sep 11, 2014

So I'm going to close this. I can see the logic behind it but ultimately I think it's going to end up with us becoming too clever and the rules for when and when a prerelease version is installed becoming hard to explain.

@dstufft dstufft closed this Sep 11, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment