[Python-Dev] Support keyword in PEP URL?

[Antoine Pitrou]

On Sat, 12 Oct 2013 14:04:48 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> On 12 Oct 2013 11:15, "Victor Stinner" <victor.stinner at gmail.com> wrote:
> >
> > 2013/10/12 Ethan Furman <ethan at stoneleaf.us>:
> > >> 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)?
> >
> > As I wrote in my first message, if changing identifier for draft PEP
> > is an issue, an option is to only add a textual identifier to accepted
> > PEPs.
> 
> RFCs are referenced by number. Standards are referenced by number.
> Nicknames are simply too ambiguous to be scalable.

Indeed. One reason is that several RFCs or PEPs may be issued for a
single topic. Which RFC gets to be called "http"? Probably the first
one, but then when you type "http" you get the HTTP 1.0 RFC. You'd
rather have the HTTP 1.1 RFC, I think. Or perhaps a further
clarification RFC.

Regards

Antoine.