A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-December/094641.html below:

[Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2

[Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2 [Python-Dev] Proposing PEP 345 : Metadata for Python Software Packages 1.2"Martin v. Löwis" martin at v.loewis.de
Thu Dec 24 10:26:55 CET 2009
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.

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4