Nick Coghlan wrote: > Steve Holden wrote: >> In which case doesn't it make more sense to use the existing mechanism >> of PEP 356 (Release Schedule)? If something isn't listed in there >> (even without dates) then there are no current plans to release it, >> and that tells the reader everything they need to know. >> >> At the moment the PEP begins with "This document describes the >> development and release schedule for Python 2.5." but it could just as >> easily say "future releases of the Python 2.X series" or something >> similar. >> >> Which reminds me, that PEP needs updating! > > Those release schedule PEPs are mainly a TODO list leading up to the > 2.x.0 releases, though - there's a new one for each major version bump: > > PEP 160 - Python 1.6 > PEP 200 - Python 2.0 > PEP 226 - Python 2.1 > PEP 251 - Python 2.2 > PEP 283 - Python 2.3 > PEP 320 - Python 2.4 > PEP 356 - Python 2.5 > PEP 361 - Python 2.6 > > Cheers, > Nick. > Thanks, it wouldn't be appropriate then (and 361 *doesn't* need updating).
regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://del.icio.us/steve.holden ------------------ Asciimercial --------------------- Get on the web: Blog, lens and tag your way to fame!! holdenweb.blogspot.com squidoo.com/pythonology tagged items: del.icio.us/steve.holden/python All these services currently offer free registration! -------------- Thank You for Reading ---------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
