On Tue, Aug 22, 2000 at 10:42:00PM -0700, Barry Warsaw wrote: > Update of /cvsroot/python/python/nondist/peps > In directory slayer.i.sourceforge.net:/tmp/cvs-serv2158 > > Modified Files: > pep-0204.txt > Log Message: > Editorial review, including: > > - Rearrange and standardize headers > - Removed ^L's > - Spellchecked > - Indentation and formatting > - Added reference to PEP 202 Damn, I'm glad I didn't rewrite it on my laptop yesterday. This looks much better, Barry, thanx ! Want to co-author it ? :) (I really need to get myself some proper (X)Emacs education so I can do cool things like two-spaces-after-finished-sentences too) > Thomas, if the open issues have been decided, they can be `closed' in > this PEP, and then it should probably be marked as Accepted. Well, that would require me to force the open issues, because they haven't been decided. They have hardly been discussed ;) I'm not sure how to properly close them, however. For instance: I would say "not now" to ranges of something other than PyInt objects, and the same to the idea of generators. But the issues remain open for debate in future versions. Should there be a 'closed issues' section, or should I just not mention them and have people start a new PEP and gather the ideas anew when the time comes ? (And a Decisions (either a consensus one or a BDFL one) would be nice on whether the two new PyList_ functions should be part of the API or not. The rest of the issues I can handle.) Don't forget, I'm a newbie in standards texts. Be gentle ;) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
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