[Python-Dev] accept the wheel PEPs 425, 426, 427 (original) (raw)
Stephen J. Turnbull stephen at xemacs.org
Sat Oct 20 06:49:08 CEST 2012
- Previous message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Next message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Holth writes:
Tweaked at http://hg.python.org/peps/rev/75474fb879d3
I'll take a look later; I have some other commitments now I should do first.
On Thu, Oct 18, 2012 at 10:55 PM, Stephen J. Turnbull <stephen at xemacs.org> wrote:
Executive summary:
You probably should include a full ABNF grammar....
The legacy PKG-INFO does not have email parse-ability. How about an example parser implementation instead, and drop email.parser.Parser() support. It will require a decent amount of additional editing.
I don't think that the example implementation matters. A strict RFC 822 email header parser that treats these as "unstructured fields" will DTRT.
The point about the ABNF grammar is based on the email community's long experience with email standards (733, 822, 2822, 5322, ...). It's always easier to relax definitions later when they prove too strict rather than tighten them up.
There is less RFC822 in the document now.
Thank you.
Typo fixed. The ability to put the full license in a separate file exists, but would be part of the .dist-info spec. These files are parsed at runtime and it's obnoxious to have long descriptions and licenses in there.
Good.
Switched to using must as in RFC MUST for extension fields ExtensionName/TagName:
Good.
Thanks for your excellent responsiveness.
- Previous message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Next message: [Python-Dev] accept the wheel PEPs 425, 426, 427
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]