Added another wish. Removed a bunch of fulfilled wishes (no guarantee
that I caught all of 'em).
This commit is contained in:
Guido van Rossum
parent
42bd6f45a7
commit
6e15da83fe
95
pep-0042.txt
95
pep-0042.txt
|
|
@ -58,16 +58,6 @@ Core Language / Builtins
|
|||
|
||||
http://www.python.org/sf/210835
|
||||
|
||||
- Add C API functions to help Windows users who are building
|
||||
embedded applications where the FILE * structure does not match
|
||||
the FILE * the interpreter was compiled with.
|
||||
|
||||
http://www.python.org/sf/210821
|
||||
|
||||
See this bug report for a specific suggestion that will allow a
|
||||
Borland C++ builder application to interact with a python.dll
|
||||
build with MSVC.
|
||||
|
||||
- The parser should handle more deeply nested parse trees.
|
||||
|
||||
The following will fail -- eval("["*50 + "]"*50) -- because the
|
||||
|
|
@ -106,17 +96,6 @@ Standard Library
|
|||
|
||||
http://www.python.org/sf/210619
|
||||
|
||||
- Use objects with attributes in place of tuples of values for
|
||||
return values in several places in the library. Two specific
|
||||
APIs which could use this treatment include os.stat() and
|
||||
os.statvfs(); see SourceForge bug #111481:
|
||||
|
||||
http://www.python.org/sf/211481
|
||||
|
||||
which shows very specifically why this approach is better than
|
||||
the tuple approach: additional attributes can be added as needed
|
||||
without having as detrimental an affect on existing code.
|
||||
|
||||
- os.rename() should be modified to handle EXDEV errors on
|
||||
platforms that don't allow rename() to operate across filesystem
|
||||
boundaries by copying the file over and removing the original.
|
||||
|
|
@ -141,15 +120,11 @@ Standard Library
|
|||
|
||||
http://www.python.org/sf/214557
|
||||
|
||||
- Port the Python SSL code to Windows.
|
||||
|
||||
http://www.python.org/sf/210683
|
||||
|
||||
- Extend Windows utime to accept directory paths.
|
||||
|
||||
http://www.python.org/sf/214245
|
||||
|
||||
- Extend copy.py to class, module & function types.
|
||||
- Extend copy.py to module & function types.
|
||||
|
||||
http://www.python.org/sf/214553
|
||||
|
||||
|
|
@ -167,6 +142,10 @@ Standard Library
|
|||
http://www.python.org/sf/215146
|
||||
http://www.python.org/sf/212244
|
||||
|
||||
Possible solution:
|
||||
|
||||
http://www.python.org/sf/474274
|
||||
|
||||
- rfc822.py should be more lenient than the spec in the types of
|
||||
address fields it parses. Specifically, an invalid address of
|
||||
the form "From: Amazon.com <delivers-news2@amazon.com>" should
|
||||
|
|
@ -237,11 +216,6 @@ Standard Library
|
|||
|
||||
http://www.python.org/sf/210838
|
||||
|
||||
- Could use a more comprehensive email module. (But then again,
|
||||
that may be better done as a 3rd party project.)
|
||||
|
||||
http://www.python.org/sf/221208
|
||||
|
||||
- every built-in function or method (including all core
|
||||
extensions) that accepts a string, dict, or list, should also
|
||||
accept a UserString, UserDict, or UserList. (The latter two
|
||||
|
|
@ -253,10 +227,6 @@ Standard Library
|
|||
|
||||
http://www.python.org/sf/426539
|
||||
|
||||
- New math module radians() and degrees() functions.
|
||||
|
||||
http://www.python.org/sf/426539
|
||||
|
||||
- Jim Fulton suggested the following:
|
||||
|
||||
I wonder if it would be a good idea to have a new kind of
|
||||
|
|
@ -290,6 +260,36 @@ Standard Library
|
|||
http://www.python.org/sf/415694
|
||||
|
||||
|
||||
C API wishes
|
||||
|
||||
- Add C API functions to help Windows users who are building
|
||||
embedded applications where the FILE * structure does not match
|
||||
the FILE * the interpreter was compiled with.
|
||||
|
||||
http://www.python.org/sf/210821
|
||||
|
||||
See this bug report for a specific suggestion that will allow a
|
||||
Borland C++ builder application to interact with a python.dll
|
||||
build with MSVC.
|
||||
|
||||
- Add unsigneds to ParseTuple/BuildValue (due to David Beazley)
|
||||
|
||||
Since "integers" can now have arbitrary precision and can
|
||||
represent large unsigned values, can you add three new format
|
||||
characters to PyArg_ParseTuple() and Py_BuildValue() for the C
|
||||
datatypes "unsigned int", "unsigned long", and "unsigned long
|
||||
long"?
|
||||
|
||||
The "u" and "l" namespace is a little crowded (and I don't think
|
||||
you would want to break that). However, here's one idea:
|
||||
|
||||
'I' - unsigned int (consistent with H and B)
|
||||
'p' - unsigned long ('p' is for positive)
|
||||
'P' - unsigned long long
|
||||
|
||||
http://www.python.org/sf/454896
|
||||
|
||||
|
||||
Tools
|
||||
|
||||
- IDLE should reload & recompile modules changed externally. To
|
||||
|
|
@ -302,29 +302,9 @@ Tools
|
|||
|
||||
http://www.python.org/sf/210820
|
||||
|
||||
- IDLE's key bindings should be revised. Some of the advertised
|
||||
bindings don't even work!
|
||||
|
||||
http://www.python.org/sf/210659
|
||||
|
||||
- IDLE has deep problems running threaded programs. Re-architect.
|
||||
|
||||
http://www.python.org/sf/221963
|
||||
|
||||
- Would be nice if IDLE showed which structure was being closed upon
|
||||
typing one of "})]". Heck, a string too, for that matter.
|
||||
The bug report also says something about TAB I didn't grok.
|
||||
|
||||
http://www.python.org/sf/404444
|
||||
|
||||
|
||||
Building and Installing
|
||||
|
||||
- You should be able to configure and build Python with a
|
||||
cross-compiler.
|
||||
|
||||
http://www.python.org/sf/210836
|
||||
|
||||
- Modules/makesetup should make sure the 'config.c' file it
|
||||
generates from the various Setup files, is valid C. It currently
|
||||
accepts module names with characters that are not allowable in
|
||||
|
|
@ -349,11 +329,6 @@ Building and Installing
|
|||
|
||||
http://www.python.org/sf/219221
|
||||
|
||||
- There should be at least an option to build Python as a shared
|
||||
library.
|
||||
|
||||
http://www.python.org/sf/400938
|
||||
|
||||
|
||||
Local Variables:
|
||||
mode: indented-text
|
||||
|
|
|
|||
Loading…
Reference in New Issue