(original) (raw)

On Sun, 17 Feb 2013 20:11:23 +1000
Nick Coghlan <ncoghlan@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@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 :-)