Move optparse and datetime to "completed"; move a bunch of other
things to "probably won't make it", mostly due to lack of energy.
This commit is contained in:
parent
6f7d1222c0
commit
bc79aa595e
94
pep-0283.txt
94
pep-0283.txt
|
@ -128,6 +128,18 @@ Completed features for 2.3
|
||||||
draft implementation in C, see http://www.python.org/sf/619475
|
draft implementation in C, see http://www.python.org/sf/619475
|
||||||
This has now been checked in.
|
This has now been checked in.
|
||||||
|
|
||||||
|
- A new command line option parser. Greg Ward's Optik package
|
||||||
|
(http://optik.sf.net) has been adopted, convert to a single
|
||||||
|
module named optparse. See also
|
||||||
|
http://www.python.org/sigs/getopt-sig/
|
||||||
|
|
||||||
|
- A standard 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. While we
|
||||||
|
may be tweaking the API during the alpha test period, I consider
|
||||||
|
this module basically complete -- except for its documentation.
|
||||||
|
|
||||||
|
|
||||||
Planned features for 2.3
|
Planned features for 2.3
|
||||||
|
|
||||||
|
@ -153,52 +165,6 @@ Planned features for 2.3
|
||||||
|
|
||||||
This looks very promising. See http://www.python.org/sf/652586
|
This looks very promising. See http://www.python.org/sf/652586
|
||||||
|
|
||||||
- A new command line option parser. Greg Ward's Optik
|
|
||||||
(http://optik.sf.net) fits the bill fine; there's only some
|
|
||||||
question about whether it should be given a less "cutesy" name.
|
|
||||||
I'm leaning toward optparse now. See also
|
|
||||||
http://www.python.org/sigs/getopt-sig/
|
|
||||||
|
|
||||||
- Provide alternatives for common uses of the types module;
|
|
||||||
Skip Montanaro has posted a proto-PEP for this idea:
|
|
||||||
http://mail.python.org/pipermail/python-dev/2002-May/024346.html
|
|
||||||
Unfortunately there hasn't been much progress on this.
|
|
||||||
|
|
||||||
- An iterator tools module featuring goodies from SML and Haskell?
|
|
||||||
http://mail.python.org/pipermail/python-dev/2002-May/024418.html
|
|
||||||
|
|
||||||
- Deprecate the buffer object.
|
|
||||||
http://mail.python.org/pipermail/python-dev/2002-July/026388.html
|
|
||||||
http://mail.python.org/pipermail/python-dev/2002-July/026408.html
|
|
||||||
No progress; the last time this was brought up only Marc-Andre
|
|
||||||
Lemburg said he had a use for it. I need to find out exactly
|
|
||||||
what that need is and how much of the buffer object we can retire.
|
|
||||||
|
|
||||||
- Add support for the long-awaited Python catalog. Kapil
|
|
||||||
Thangavelu has a Zope-based implementation that he demoed at
|
|
||||||
OSCON 2002. Now all we need is a place to host it and a person
|
|
||||||
to champion it.
|
|
||||||
|
|
||||||
- A standard datetime type. An implementation effort is under way:
|
|
||||||
http://www.zope.org/Members/fdrake/DateTimeWiki/FrontPage
|
|
||||||
There's a prototype implementation in nondist/sandbox/datetime/.
|
|
||||||
Tim Peters is committed to finishing the C implementation.
|
|
||||||
Effbot and MAL have a proposal for a basic interface that all
|
|
||||||
datetime types should implement, but there are some problems with
|
|
||||||
UTC. A decision needs to be made.
|
|
||||||
|
|
||||||
- Decide on a clearer deprecation policy (especially for modules)
|
|
||||||
and act on it. For a start, see this message from Neil Norwitz:
|
|
||||||
http://mail.python.org/pipermail/python-dev/2002-April/023165.html
|
|
||||||
|
|
||||||
- Use pending deprecation for the types and string modules. This
|
|
||||||
requires providing alternatives for the parts that aren't
|
|
||||||
covered yet (e.g. string.whitespace and types.TracebackType).
|
|
||||||
|
|
||||||
- PEP 269 Pgen Module for Python Riehl
|
|
||||||
|
|
||||||
Jon Riehl is going to attempt an implementation by mid-September.
|
|
||||||
|
|
||||||
- Documentation: complete the distribution and installation
|
- Documentation: complete the distribution and installation
|
||||||
manuals.
|
manuals.
|
||||||
|
|
||||||
|
@ -215,7 +181,7 @@ Planned features for 2.3
|
||||||
|
|
||||||
- Document deprecated features appropriately.
|
- Document deprecated features appropriately.
|
||||||
|
|
||||||
- Move deprecated features under Py_DEPRECATED (or whatever is decided)
|
- Mark deprecated C APIs with Py_DEPRECATED.
|
||||||
|
|
||||||
- Deprecate modules which are unmaintained, or perhaps make a new
|
- Deprecate modules which are unmaintained, or perhaps make a new
|
||||||
category for modules 'Unmaintained'
|
category for modules 'Unmaintained'
|
||||||
|
@ -225,6 +191,40 @@ Planned features for 2.3
|
||||||
|
|
||||||
Features unlikely to make it into Python 2.3
|
Features unlikely to make it into Python 2.3
|
||||||
|
|
||||||
|
- Decide on a clearer deprecation policy (especially for modules)
|
||||||
|
and act on it. For a start, see this message from Neil Norwitz:
|
||||||
|
http://mail.python.org/pipermail/python-dev/2002-April/023165.html
|
||||||
|
There seems insufficient interest in moving this further in an
|
||||||
|
organized fashion, and it's not particularly important.
|
||||||
|
|
||||||
|
- Provide alternatives for common uses of the types module;
|
||||||
|
Skip Montanaro has posted a proto-PEP for this idea:
|
||||||
|
http://mail.python.org/pipermail/python-dev/2002-May/024346.html
|
||||||
|
There hasn't been any progress on this, AFAICT.
|
||||||
|
|
||||||
|
- Use pending deprecation for the 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.
|
||||||
|
|
||||||
|
- An iterator tools module featuring goodies from SML and Haskell?
|
||||||
|
http://mail.python.org/pipermail/python-dev/2002-May/024418.html
|
||||||
|
I haven't heard about this in ages.
|
||||||
|
|
||||||
|
- Deprecate the buffer object.
|
||||||
|
http://mail.python.org/pipermail/python-dev/2002-July/026388.html
|
||||||
|
http://mail.python.org/pipermail/python-dev/2002-July/026408.html
|
||||||
|
It seems that this is never going to be resolved.
|
||||||
|
|
||||||
|
- PEP 269 Pgen Module for Python Riehl
|
||||||
|
|
||||||
|
I haven't heard from Jon Riehl since he moved to Chicago.
|
||||||
|
|
||||||
|
- Add support for the long-awaited Python catalog. Kapil
|
||||||
|
Thangavelu has a Zope-based implementation that he demoed at
|
||||||
|
OSCON 2002. Now all we need is a place to host it and a person
|
||||||
|
to champion it.
|
||||||
|
|
||||||
- PEP 266 Optimizing Global Variable/Attribute Access Montanaro
|
- PEP 266 Optimizing Global Variable/Attribute Access Montanaro
|
||||||
PEP 267 Optimized Access to Module Namespaces Hylton
|
PEP 267 Optimized Access to Module Namespaces Hylton
|
||||||
PEP 280 Optimizing access to globals van Rossum
|
PEP 280 Optimizing access to globals van Rossum
|
||||||
|
|
Loading…
Reference in New Issue