[Python-checkins] python/nondist/peps pep-0283.txt,1.28,1.29

2003年2月01日 11:02:12 -0800

Update of /cvsroot/python/python/nondist/peps
In directory sc8-pr-cvs1:/tmp/cvs-serv17078
Modified Files:
	pep-0283.txt 
Log Message:
Remove text about new pickling; refer to PEP 307 instead.
Index: pep-0283.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0283.txt,v
retrieving revision 1.28
retrieving revision 1.29
diff -C2 -d -r1.28 -r1.29
*** pep-0283.txt	7 Jan 2003 02:23:50 -0000	1.28
--- pep-0283.txt	1 Feb 2003 19:02:10 -0000	1.29
***************
*** 27,35 ****
 guidelines:

! alpha 2 -- late January
! beta 1 -- late February
! beta 2 -- late March
! rc 1 -- late April
! final -- early May

--- 27,35 ----
 guidelines:

! alpha 2 -- mid February
! beta 1 -- mid March
! beta 2 -- mid April
! rc 1 -- mid May
! final -- end of May

***************
*** 39,72 ****

- Open issues
- 
- There are some issues that may need more work and/or thought
- before the final release (and preferably before the first beta
- release). For example:
- 
- - Set API issues; is the sets module perfect?
- 
- I expect it's good enough to stop polishing it until we've had
- more widespread user experience.
- 
- - A nicer API to open text files, replacing the ugly (in some
- people's eyes) "U" mode flag. There's a proposal out there to
- have a new built-in type textfile(filename, mode, encoding).
- (Shouldn't it have a bufsize argument too?)
- 
- Ditto.
- 
- - Fredrik Lundh's basetime proposal:
- http://effbot.org/ideas/time-type.htm
- 
- I believe this is dead now.
- 
- - New widgets for Tkinter???
- 
- 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).
- 
- 
 Completed features for 2.3

--- 39,42 ----
***************
*** 179,217 ****
 life of the 2.3 development process.

! - reST is going to be used a lot in Zope3. Maybe it could become
! a standard library module?
! 
! - I really, really, really would like to improve pickling of
! new-style classes.
! 
! I've finally come to the conclusion that any solution to making
! pickled new-style class instances (and hence pickled datetime
! objects) more efficient will require adding new codes to the
! pickle protocol.
! 
! We can do that in Python 2.3. Because this is backwards
! incompatible, I propose that you have to request this protocol
! explicitly. I propose to "upgrade' the binary flag to a general
! "protocol version" flag, with values:
! 
! 0 - original protocol
! 1 - binary protocol
! 2 - new protocol
! 
! The new protocol can contain an explicit pickle code for the new
! datetime objects. That's about all the thinking I've done so
! far. We need to decide on the new format, but first we must
! figure out ways how to efficiently pickle and unpickle subclass
! instances of (picklable) built-in types, preferably without
! having to copy all the data twice, and instances of new-style
! classes with slots. And we need to implement these twice: in
! Python for pickle.py and in C for cPickle.py.
! 
! - I'd also like to get rid of __safe_for_unpickling__ and all
! other pseudo security features. Attempting to unpickle pickles
! from an untrusted source is insane, and nothing can help us
! there; I'd rather make the marshal protocol bulletproof (all it
! needs is a few more checks for inconsistent data and a little
! better error handling).

 - For a class defined inside another class, the __name__ should be
--- 149,153 ----
 life of the 2.3 development process.

! - A new pickling protocol. See PEP 307.

 - For a class defined inside another class, the __name__ should be
***************
*** 248,252 ****
--- 184,222 ----

+ Open issues
+ 
+ There are some issues that may need more work and/or thought
+ before the final release (and preferably before the first beta
+ release). For example:
+ 
+ - Set API issues; is the sets module perfect?
+ 
+ I expect it's good enough to stop polishing it until we've had
+ more widespread user experience.
+ 
+ - A nicer API to open text files, replacing the ugly (in some
+ people's eyes) "U" mode flag. There's a proposal out there to
+ have a new built-in type textfile(filename, mode, encoding).
+ (Shouldn't it have a bufsize argument too?)
+ 
+ Ditto.
+ 
+ - Fredrik Lundh's basetime proposal:
+ http://effbot.org/ideas/time-type.htm
+ 
+ I believe this is dead now.
+ 
+ - New widgets for Tkinter???
+ 
+ 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).
+ 
+ 
 Features unlikely to make it into Python 2.3
+ 
+ - reST is going to be used a lot in Zope3. Maybe it could become
+ a standard library module? (Since reST's author thinks it's too
+ instable, I'm inclined not to do this.)

 - Decide on a clearer deprecation policy (especially for modules)