This document describes the development and release schedule for Python 2.3. The schedule primarily concerns itself with PEP-sized items. Small features may be added up to and including the first beta release. Bugs may be fixed until the final release.
There will be at least two alpha releases, two beta releases, and one release candidate. Alpha and beta releases will be spaced at least 4 weeks apart (except if an emergency release must be made to correct a blunder in the previous release; then the blunder release does not count). Release candidates will be spaced at least one week apart (excepting again blunder corrections).
alpha 1 31 Dec 2002 alpha 2 19 Feb 2003 beta 1 25 Apr 2003 beta 2 29 Jun 2003 candidate 1 18 Jul 2003 candidate 2 24 Jul 2003 final 29 Jul 2003 Release ManagerBarry Warsaw, Jeremy Hylton, Tim Peters
Completed features for 2.3This list is not complete. See Doc/whatsnew/whatsnew23.tex in CVS for more, and of course Misc/NEWS for the full list.
bool type and its constants, True and False (PEP 285).PyMalloc was greatly enhanced and is enabled by default.Implemented (at least phase 1, which is all that’s planned for 2.3).
tp_iter and other tweaks. See https://bugs.python.org/issue560736; also done for xrange and tuples.int/long integration (PEP 237). This means issuing a FutureWarning about situations where hex or oct conversions or left shifts returns a different value for an int than for a long with the same value. The semantics do not change in Python 2.3; that will happen in Python 2.4.SET_LINENO from all code objects (providing a different way to set debugger breakpoints). This can boost pystone by >5%. https://bugs.python.org/issue587993, now checked in. (Unfortunately the pystone boost didn’t happen. What happened?)pymemcompat.h that people can bundle with their extensions and then use the 2.3 memory interface with all Pythons in the range 1.5.2 to 2.3. (Michael Hudson checked in Misc/pymemcompat.h.)PendingDeprecationWarning. This warning is normally suppressed, but can be enabled by a suitable -W option. Only a few things use this at this time.tp_compare returns anything except -1, 0 or 1. https://bugs.python.org/issue472523None (in various forms).Alex Martelli contributed a new version of Greg Wilson’s prototype, and I’ve reworked that quite a bit. It’s in the standard library now as the module sets, although some details may still change until the first beta release. (There are no plans to make this a built-in type, for now.)
Fully implemented. Error handling in unicode.encode or str.decode can now be customized.
Vinay Sajip’s implementation has been packagized and imported. (Documentation and unit tests still pending.) https://bugs.python.org/issue578494
optparse. See also http://www.python.org/sigs/getopt-sig/datetime type. This started as a wiki: http://www.zope.org/Members/fdrake/DateTimeWiki/FrontPage. A prototype was coded in nondist/sandbox/datetime/. Tim Peters has finished the C implementation and checked it in.Implemented as a part of the PEP 302 implementation work.
Implemented (though the 2.3a1 release contained some bugs that have been fixed post-release).
itertools module is in.PyArg_Parse*() format codes, ‘k’ returns an unsigned C long int that receives the lower LONG_BIT bits of the Python argument, truncating without range checking. ‘K’ returns an unsigned C long long int that receives the lower LONG_LONG_BIT bits, truncating without range checking. (SF 595026; Thomas Heller did this work.)idlelib package in the standard library and the idle script is installed by setup.py.Too late for anything more to get done here.
Ongoing tasksThe following are ongoing TO-DO items which we should attempt to work on without hoping for completion by any particular date.
Demos/ directory and update where required (Andrew Kuchling has done a lot of this)Py_DEPRECATED.There are some issues that may need more work and/or thought before the final release (and preferably before the first beta release): No issues remaining.
Features that did not make it into Python 2.3I expect it’s good enough to stop polishing it until we’ve had more widespread user experience.
textfile(filename, mode, encoding). (Shouldn’t it have a bufsize argument too?)
Ditto.
Has anyone gotten the time for this? Are there any new widgets in Tk 8.4? Note that we’ve got better Tix support already (though not on Windows yet).
http://effbot.org/ideas/time-type.htm
I believe this is dead now.
__name__ should be "outer.inner", and pickling should work. (SF 633930. I’m no longer certain this is easy or even right.)types module;
Skip Montanaro has posted a proto-PEP for this idea: https://mail.python.org/pipermail/python-dev/2002-May/024346.html
There hasn’t been any progress on this, AFAICT.
types and string modules. This requires providing alternatives for the parts that aren’t covered yet (e.g. string.whitespace and types.TracebackType). It seems we can’t get consensus on this.buffer object.
It seems that this is never going to be resolved.
(Some necessary changes are in; the pgen module itself needs to mature more.)
PEP 267 Optimized Access to Module Namespaces, Hylton
PEP 280 Optimizing access to globals, van Rossum
These are basically three friendly competing proposals. Jeremy has made a little progress with a new compiler, but it’s going slow and the compiler is only the first step. Maybe we’ll be able to refactor the compiler in this release. I’m tempted to say we won’t hold our breath. In the meantime, Oren Tirosh has a much simpler idea that may give a serious boost to the performance of accessing globals and built-ins, by optimizing and inlining the dict access: http://tothink.com/python/fastnames/
Not much enthusiasm I believe.
I haven’t had the time to review this thoroughly. It seems a deep optimization hack (also makes better correctness guarantees though).
This document has been placed in the public domain.
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