'pip install' without '--pre' option should not install pre-release versions if possible

[msmhrt]

Currently, pip install "logya>=2.1beta1" installs logya-3.0beta1 instead of logya-2.3.
I think pip install without --pre option should not install pre-release versions if possible.

$ pip install "logya>=3.0beta0" # installs logya-3.0beta1 and It's OK because logya-3.0 is not released yet.
$ pip uninstall logya
$ pip install "logya>=2.1" # installs logya-2.3 and It's OK.
$ pip uninstall logya
$ pip install "logya>=2.1.beta1" # installs logya-3.0beta1 instead of logya-2.3

OS: Ubuntu 12.04 (64-bit)
python: 2.7.6
setuptools: 2.1.2
pip: HEAD of develop branch

[dstufft]

I'm going to say that this is going to be wontfix. The problem is this is going to be a special case for one particular time, however lots of other times it won't make any sense. Because of that IMO this should be a wonfix.

[msmhrt]

I don't think that it is a special case.
For example, if you want to use 'enum' module the new features in Python 3.4 before Python 3.4 release, you may have no choice but to use "Python>=3.4rc1".
(Python isn't module, of course.)

But, If Python 3.5b1 is released, "Python>=3.4rc1" installs 3.5b1 and then you will be in trouble.
So, I think pip install without --pre option should not install pre-release versions if possible.

[Ivoz]

"Python>=3.4rc1"

Do you mean to use an example of the enum package? It's already at a stable 0.4.4

[msmhrt]

No, of course I know Python isn't a module, but I can not think of a better example module.

[ghost]

Dies pip install prerelease versions by default "latest"? That seems really dangerous.

[dholth]

It only installs prerelease versions if you asked for >= (a prerelease version). >= (a normal version) will do what was expected.