On Oct 11, 2013, at 9:13 PM, Victor Stinner <victor.stin...@gmail.com> wrote:
> 2013/10/12 Ethan Furman <et...@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. > >> For than matter, what names would you give to the myriad unicode peps? > > Let me try to name PEPs related to Unicode: > > 100: unicode_integration > 261: unicode_ucs4 > 277: windows_unicode_filenames (hum, I proposed a limit of 20 > characters, this name is 25 characters long) > 383: surrogateescape > 393: compact_unicode > 414: u_prefix_py33 > > These names are just propositions. They should be discussed :-) Perhaps we can have a PEP to decide the name of a PEP! > > (they are probably much more PEPs related to Unicode :-)) > > Victor > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/donald%40stufft.io ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
