Changes:
http://pypi.python.org/pypi/zc.buildout/2.0.0b2#b2-2013-02-02
This release adds features from buildout-versions. Much thanks
to Reinout van Rees for doing this work and doing it so quickly.
If problems aren't discovered first, I plan to make the final release
next weekend.
To
a top level dev release should be sorted before the first alpha
release
ok, so applying this to the example in pep386 (and your comment about
interpreting a top-level dev as a0.dev), the sorting would be like
this?
new... V('1.0dev1')
new... V('1.0a0.dev2')
new...
The problem with allowing both pre and dev (as suggested last
year) is that it's completely unclear how to sort them when they
appear at the same level. Does dev come before pre or after?
here's the suggestion I think from the old thread.
* dev should be moved to a main** release type sorted
with the modification that when a tool sees an unqualified X.Y.dev
or X.Y.Z.dev release (i.e. any release where the dev immediately
follows the purely numeric component of the version), that should be
reinterpreted as if there was an a0 component (as in X.Y.a0.dev or
X.Y.Z.a0.dev) between the
On Sun, Feb 3, 2013 at 9:06 AM, Marcus Smith qwc...@gmail.com wrote:
a top level dev release should be sorted before the first alpha
release
ok, so applying this to the example in pep386 (and your comment about
interpreting a top-level dev as a0.dev), the sorting would be like this?
No, all the dev releases will sort before all the a releases (and
PEP 426 will be explicit about that).
ok, there's top-level dev and then there's .dev
see my other comments about being unclear what you're saying given the
typos.
maybe rewrite the pep386 example for us in this email so it's
In re-reading PEP 386, I noticed that the Version Specifiers section
explicitly excludes post releases like 2.5.post1 or 2.5.1.post1
from matching a request for 2.5. I can understand excluding all
pre-releases from a general request like 2.5, but why exclude post
releases? Aren't those intended to
On Sunday, February 3, 2013 at 12:43 AM, Nick Coghlan wrote:
In re-reading PEP 386, I noticed that the Version Specifiers section
explicitly excludes post releases like 2.5.post1 or 2.5.1.post1
from matching a request for 2.5. I can understand excluding all
pre-releases from a general request
On Sun, Feb 3, 2013 at 3:23 PM, Marcus Smith qwc...@gmail.com wrote:
No, all the dev releases will sort before all the a releases (and
PEP 426 will be explicit about that).
ok, there's top-level dev and then there's .dev
see my other comments about being unclear what you're saying given the
just re-merged qwcode/pip/wheel_install with pypa/pip/develop.
https://github.com/qwcode/pip
tests are passing (using the latest wheel-0.15.0)
here's the pip wheel usage doc:
http://qwcode.com/pip/usage.html#pip-wheel
and the example on using pip to build wheels from your requirements and
then
On Sat, Feb 2, 2013 at 11:39 PM, Marcus Smith qwc...@gmail.com wrote:
just re-merged qwcode/pip/wheel_install with pypa/pip/develop.
to be clearer, merged pypa/pip/develop *into* qwcode/pip/develop
not the other way... : )
Marcus
___
to be clearer, merged pypa/pip/develop *into* qwcode/pip/develop
jeez, I can't say this right, sorry.
merged pypa/pip/develop *into* qwcode/pip/wheel_install
Marcus
___
Distutils-SIG maillist - Distutils-SIG@python.org
12 matches
Mail list logo
