[Python-Dev] PEP 426 is now the draft spec for distribution metadata 2.0 (original) (raw)
Daniel Holth dholth at gmail.com
Sun Feb 17 19:45:00 CET 2013
- Previous message: [Python-Dev] PEP 426 is now the draft spec for distribution metadata 2.0
- Next message: [Python-Dev] PEP 426 is now the draft spec for distribution metadata 2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, 17 Feb 2013 20:11:23 +1000 Nick Coghlan <ncoghlan at gmail.com> wrote:
Major changes since the last draft: 1. Metadata-Version is 2.0 rather than 1.3, and the field now has the same major.minor semantics as are defined for wheel versions in PEP 427 (i.e. if a tool sees a major version number it doesn't recognise, it should give up rather than trying to guess what to do with it, while it's OK to process a higher minor version)
So is it possible to bundle several versioned metadata files in order to maximize compatibility? Or does a distribution with 2.0 metadata have to abandon all hope of being compatible with all tools?
Regards
Antoine.
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/dholth%40gmail.com
Not likely to matter for a while as the current md v1 tools don't understand this new obsolescence rule :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130217/a9ed4e25/attachment.html>
- Previous message: [Python-Dev] PEP 426 is now the draft spec for distribution metadata 2.0
- Next message: [Python-Dev] PEP 426 is now the draft spec for distribution metadata 2.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]