[Python-Dev] Support keyword in PEP URL?
Ethan Furman
ethan at stoneleaf.us
Sat Oct 12 03:01:08 CEST 2013
On 10/11/2013 04:35 PM, Ben Finney wrote:
> 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?
Heh, that was the same example I was going to use. :)
Another question: if the later PEP gets the appropriate name, what name then gets applied to the older one(s)?
For than matter, what names would you give to the myriad unicode peps?
--
~Ethan~
More information about the Python-Dev
mailing list