I've received a request that pip be able to be restricted to "stable"
versions. It was suggested some kind of --alpha-ok or --beta-ok option,
but this seems crude. I'd rather have it be part of the requirement.
Maybe Package==stable? But there's also reason to do something like
Package>=2.0,
At 06:44 PM 12/16/2008 -0600, Ian Bicking wrote:
I've received a request that pip be able to be restricted to
"stable" versions. It was suggested some kind of --alpha-ok or
--beta-ok option, but this seems crude. I'd rather have it be part
of the requirement. Maybe Package==stable? But there
Phillip J. Eby wrote:
At 06:44 PM 12/16/2008 -0600, Ian Bicking wrote:
I've received a request that pip be able to be restricted to "stable"
versions. It was suggested some kind of --alpha-ok or --beta-ok
option, but this seems crude. I'd rather have it be part of the
requirement. Maybe Pack
On Tue, Dec 16, 2008 at 7:44 PM, Ian Bicking wrote:
> Also, there needs to be a definition of what versions are "stable". And
> maybe a distinction between beta/rc and development, though I'm less worried
> about that. Are there definitions of this? Does zc.buildout do this?
http://pypi.pytho
Ian Bicking writes:
> Also, there needs to be a definition of what versions are "stable".
> And maybe a distinction between beta/rc and development, though I'm
> less worried about that. Are there definitions of this?
A further complication: If “Foo” at its latest stable version has a
dependenc
