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/2013-October/129440.html below:

[Python-Dev] Support keyword in PEP URL?

[Python-Dev] Support keyword in PEP URL? [Python-Dev] Support keyword in PEP URL?Ben Finney ben+python at benfinney.id.au
Sat Oct 12 01:35:14 CEST 2013
Victor Stinner <victor.stinner at gmail.com> writes:

> For draft PEP, the identifier may change.

For an idea implemented in several PEPs, the obvious identifier may be
taken first, but the preferred PEP for that identifier may later change.

For example, PEP 354 would have the obvious keyword “enum” when it was
being discussed. Then it was rejected.

Later, PEP 435 was introduced, and accepted. It is now even *more*
deserving of the keyword “enum” than the earlier PEP.

What do you propose in cases like this? Should the keyword always refer
to the same PEP it did in the past, even when that PEP is no longer as
relevant given later PEPs? Or should the keyword reach a different,
newer PEP if that newer PEP becomes a “more relevant” PEP for the
keyword?

-- 
 \        “There are only two ways to live your life. One is as though |
  `\          nothing is a miracle. The other is as if everything is.” |
_o__)                                                 —Albert Einstein |
Ben Finney

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