I followed in the past the discussion that lead to the pep. I've lost any
interest in it because I had a clear perception there was more interest in
splitting the hair that solving any real problem, *and that was years ago*.
That alone should trigger some doubt about the validity of the points
On Tuesday, February 5, 2013 at 5:35 AM, a.cava...@cavallinux.eu wrote:
Ideally it would be something that connects to the source revision number (as
in
subversion) or the integral id or even a timestamp (that's what an exported
version must be).
Timestamp or reversion number is not overall
On Tue, Feb 5, 2013 at 7:54 AM, Donald Stufft donald.stu...@gmail.comwrote:
On Tuesday, February 5, 2013 at 5:35 AM, a.cava...@cavallinux.eu wrote:
Ideally it would be something that connects to the source revision number
(as in
subversion) or the integral id or even a timestamp (that's
On Tuesday, February 5, 2013 at 9:08 AM, Daniel Holth wrote:
What if we replaced this with semver? Last fall I argued that PEP 386 sucked
and that we should use semver. Unfortunately semver is less similar to the
longstanding sort order than the proposed scheme, there would be a lot of -
Not quite correct: 1.1.x and 1.2.x are two separate branches in Django.
So along the 1.1.x branch the timestamp identifies what comes first and after.
Think of a plane where the coordinates are the timestamp and the branch: to
compare you need fix one of the two (the branch in this case).
BTW
On Wed, Feb 6, 2013 at 12:15 AM, a.cava...@cavallinux.eu wrote:
Not quite correct: 1.1.x and 1.2.x are two separate branches in Django.
So along the 1.1.x branch the timestamp identifies what comes first and after.
Think of a plane where the coordinates are the timestamp and the branch: to
On Tue, Feb 5, 2013 at 3:08 PM, Daniel Holth dho...@gmail.com wrote:
The marketing pre-release feature exists to allow publishers to put
immature versions of their software on pypi where they can be easily
downloaded. Recently SQLAlchemy did this but had to delete the beta release
from pypi
On Wed, Feb 6, 2013 at 1:06 AM, Philippe Ombredanne
pombreda...@nexb.com wrote:
On Tue, Feb 5, 2013 at 3:08 PM, Daniel Holth dho...@gmail.com wrote:
The marketing pre-release feature exists to allow publishers to put
immature versions of their software on pypi where they can be easily
I respectfully disagree, for what it matters I will ignore the whole stuff.
These PEPs have been around for ages. And I supsect they will be around until
the
end of times.
Or until when somebody will explain if X.Y.devN comes before of after X.Y.N...
On Tue 05/02/13 15:44, Nick Coghlan
On Tuesday, February 5, 2013 at 10:49 AM, a.cava...@cavallinux.eu wrote:
Or until when somebody will explain if X.Y.devN comes before of after X.Y.N...
Easy, before.
___
Distutils-SIG maillist - Distutils-SIG@python.org
What if pip did not depend on setuptools or distutils and the stdlib
did not include distutils or any other build system? Instead, the
installer can only install binary packages, and build systems do not
install but only build binary packages.
A very simple meta-build system mebs is used to
11 matches
Mail list logo
