[Python-Dev] Edits to Metadata 1.2 to add extras (optional ependencies) (original) (raw)
Daniel Holth dholth at gmail.com
Fri Aug 31 13:01:17 CEST 2012
- Previous message: [Python-Dev] Edits to Metadata 1.2 to add extras (optional ependencies)
- Next message: [Python-Dev] Edits to Metadata 1.2 to add extras (optional ependencies)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Aug 31, 2012, at 6:54 AM, Donald Stufft <donald.stufft at gmail.com> wrote:
On Friday, August 31, 2012 at 6:48 AM, "Martin v. Löwis" wrote:
3. There should be a specification of how collisions between extension fields and standard fields are resolved. E.g. if I have
Extension: Home Home-page: http://www.python.org is Home-page the extension field or the PEP 345 field? There are several ways to resolve this; I suggest giving precedence to the standard field (unless you specify that extensions must follow all standard fields, in which case you can drop the extension prefix from the extension keys). Unless i'm mistaken (which I may be!) I believe that a / can be used as the separator between the namespace and the "real" key. Home-page: http://www.python.org Extension: Home Home/other-thing: Foo
Not bad.
Doing this is the "Extension" field required?
Yes it is required. A simple lookup for data ['extension'] tells you what to expect. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120831/002b8e11/attachment.html>
- Previous message: [Python-Dev] Edits to Metadata 1.2 to add extras (optional ependencies)
- Next message: [Python-Dev] Edits to Metadata 1.2 to add extras (optional ependencies)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]