Moderate first formatting pass of Jeremy's content for this PEP.
This commit is contained in:
parent
d96183f255
commit
76592cc75b
59
pep-0200.txt
59
pep-0200.txt
|
@ -1,7 +1,7 @@
|
|||
PEP: 200
|
||||
Title: Python 2.0 Release Schedule
|
||||
Version: $Revision$
|
||||
Owner: bwarsaw@beopen.com (Barry A. Warsaw)
|
||||
Owner: Jeremy Hylton <jeremy@beopen.com>
|
||||
Python-Version: 2.0
|
||||
Status: Incomplete
|
||||
|
||||
|
@ -14,6 +14,63 @@ Introduction
|
|||
CVS revision history of this file contains the definitive
|
||||
historical record.
|
||||
|
||||
Accepted and completed
|
||||
|
||||
Accepted and in progress
|
||||
|
||||
* SyntaxError enhancements - Fredrik Lundh
|
||||
http://www.python.org/pipermail/python-dev/2000-July/012981.html
|
||||
|
||||
* interface to poll system call - Andrew Kuchling
|
||||
An OO interface to the poll system call will be added to the
|
||||
select module.
|
||||
|
||||
* Compression of Unicode database - Fredrik Lundh
|
||||
http://hem.passagen.se/eff/bot.htm#456806
|
||||
|
||||
* SRE - Fredrik Lundh
|
||||
The test suite still fails on test_re.
|
||||
|
||||
* snprintf - owner???
|
||||
Use snprintf to avoid buffer overflows. Need configure hackery
|
||||
to discovery if it is available on the current platform and a
|
||||
default implementation if it is not.
|
||||
http://www.python.org/pipermail/python-dev/2000-April/010051.html
|
||||
This function is expected to be part of C9X (check).
|
||||
|
||||
* Support for opcode arguments > 2**16 - Charles Waldman
|
||||
Source files longer than 32K and sequences with more than 32K
|
||||
elements both fail because opcode arguments are limited to
|
||||
16-bit values.
|
||||
|
||||
* Range literals - Thomas Wouters
|
||||
Make range(1, 10, 2) == [1:10:2]
|
||||
|
||||
Open: proposed but not accepted or declined
|
||||
|
||||
* List comprehensions - Tim Peters?
|
||||
Need a coherent proposal. Lots of confusing discussion going
|
||||
on.
|
||||
|
||||
* Eliminated SET_LINENO opcode - Vladimir Marangozov
|
||||
Small optimization achieved by using the code object's lnotab
|
||||
instead of the SET_LINENO instruction. Uses code rewriting
|
||||
technique (that Guido's growns on) to support debugger, which
|
||||
uses SET_LINENO.
|
||||
|
||||
http://starship.python.net/~vlad/lineno/
|
||||
for (working at the time) patches
|
||||
|
||||
Discussions on python-dev:
|
||||
|
||||
- http://www.python.org/pipermail/python-dev/2000-April/subject.html
|
||||
Subject: "Why do we need Traceback Objects?"
|
||||
|
||||
- http://www.python.org/pipermail/python-dev/1999-August/002252.html
|
||||
|
||||
Declined
|
||||
|
||||
|
||||
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
|
|
Loading…
Reference in New Issue