On Thu, 11 Aug 2005 08:47:37 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= <[EMAIL PROTECTED]> wrote:
>Micah Elliott wrote: >> I also have this living as a wiki <http://tracos.org/codetag/wiki/Pep> >> if people would like to add comments there. I might try to capture there >> feedback from this group anyway. First try at a PEP -- thanks for any >> feedback! > >I think you somewhat misunderstood the purpose of the PEP process. >This is meant primarily for enhancements to Python (the language >and its library), and it is meant to save the PEP author from >implementing unagreeable functionality - if the PEP is accepted, >the PEP author is typically expected to implement the proposed >functionality (in many cases, having a draft implementation is >prerequisite to accepting it). > >Both elements seem to be missing your document: it does not propose >changes to the Python language; instead, it proposes a specific >way of writing comments (ie. something that is not relevant to the >Python interpreter or libraries, only to the Python developer). Erm, (cough) PEP 263 specifies comment syntax ;-) But I agree that the OP's proposal is not a core language matter. Perhaps this is another PEEP candidate (i.e., a "Python Evironment Enhancement Proposal" to put in a "PEEP" application/tools/environment-oriented clone of the PEP process). Maybe a PEEP top page in the wiki with links to specific PEEPs could be a way to try it out. Regards, Bengt Richter -- http://mail.python.org/mailman/listinfo/python-list
