[Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2 (original) (raw)
Tarek Ziadé ziade.tarek at gmail.com
Thu Dec 24 10:52:22 CET 2009
- Previous message: [Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2
- Next message: [Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Dec 24, 2009 at 10:26 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
David Lyon wrote:
On Thu, 24 Dec 2009 10:31:09 +0900, "Stephen J. Turnbull" <stephen at xemacs.org> wrote:
Martin's point is that the PEP process doesn't have "reference" implementations. It has sample implementations. It may be useful to refer to a sample implementation as an example.. Fair enough. But otoh, asking for sample implementations on this type of project can skew the PEP towards a particular implementation or product. Nobody is "asking" for sample implementations. Instead, I'm asking that what Tarek calls a "reference implementation" should be called a "sample implementation" instead. I'm asking for that precisely to avoid a skew towards a particular implementation.
I'll remove it and push it in Distutils documentation, then might just provide a link in the PEP References.
Tarek
- Previous message: [Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2
- Next message: [Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]