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.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
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