Hi all,
The initial draft of Python's next generation metadata standard is up on
python.org:
PEP 426 (metadata 2.0): http://www.python.org/dev/peps/pep-0426/
PEP 440 (versioning): http://www.python.org/dev/peps/pep-0440/
The rationale for many of the changes is at the end of each PEP, along
with some comments on features that I have either rejected or
deliberately chosen to defer to the next revision of the metadata (at
the earliest).
Those with BitBucket accounts may also comment inline on the drafts here:
PEP 426:
https://bitbucket.org/ncoghlan/misc/src/05d3586464b10d6a04a35409468269d7c89a87ba/pep_drafts/pep-0426.txt?at=default
PEP 440:
https://bitbucket.org/ncoghlan/misc/src/05d3586464b10d6a04a35409468269d7c89a87ba/pep_drafts/pep-0440.txt?at=default
The distutils-sig thread is here:
http://mail.python.org/pipermail/distutils-sig/2013-May/020863.html
Possible changes already being discussed:
* Contact metadata:
"type" -> "role"
"individual" -> "contributor"
Lose the "organization" type (allows orgs to be entered for any role)
* New top level field "distributes"
Like "requires", but doesn't discourage version pinning
Used for metapackages (like PyObjC)
May map nicely to software collections
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Test Automation Team Lead
Beaker Development Lead (http://beaker-project.org/)
PulpDist Development Lead (http://pulpdist.readthedocs.org)
_______________________________________________
python-devel mailing list
python-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/python-devel
