[Distutils] PEP 426 updated (with more than you ever wanted to know about version schemes)

Daniel Holth dholth at gmail.com
Tue Feb 12 05:01:14 CET 2013

On Mon, Feb 11, 2013 at 10:18 PM, Daniel Holth <dholth at gmail.com> wrote:

> On Mon, Feb 11, 2013 at 1:37 PM, Marcus Smith <qwcode at gmail.com> wrote:
>> >> Projects which wish to use non-compliant version identifiers must
>> restrict themselves to metadata v1.1
>> currently, "Projects" don't have control over this, right?
>> setuptools/distutils just writes 1.0 or 1.1 metadata, period.
>> maybe that can be clarified for me and others.
>> what can a project really do right now to use v1.3?  nothing, except wait
>> for tool chain updates?
I've taken the language out. Wacky versions will not sort correctly with
installers no matter which metadata is being used and you don't really get
to choose your metadata version.

Setup-Requires-Dist doesn't need to support extras aka Provides-Extra aka
optional features. It would have been a new feature and would probably
cause trouble with workflows like "setup [extras] build a binary package"
and then "install [with different extras] the binary package"

Provides-Dist does not need to repeat the project's name. Does RPM do this?
If you are writing Metadata 1.3 by hand it would just feel silly to type
the name twice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130211/e679170e/attachment.html>

More information about the Distutils-SIG mailing list