[Python-checkins] CVS: python/dist/src PLAN.txt,1.15,1.16

[Guido van Rossum]

Update of /cvsroot/python/python/dist/src
In directory usw-pr-cvs1:/tmp/cvs-serv10990

Modified Files:
	PLAN.txt 
Log Message:
Update.  __dict__ assignment done.  Reorder remaining "to do" items by
priority.  Add tp_cache; add some comments to others.


Index: PLAN.txt
===================================================================
RCS file: /cvsroot/python/python/dist/src/PLAN.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** PLAN.txt	2001/10/12 17:43:43	1.15
--- PLAN.txt	2001/10/26 04:31:54	1.16
***************
*** 2,18 ****
  ****************************
  
! Still to do
! -----------
! 
! Add __del__ handlers?
  
! Allow assignment to __bases__ and __dict__?
  
  Support mixed multiple inheritance from classic and new-style classes?
  
  Check for conflicts between base classes.  I fear that the rules used
  to decide whether multiple bases have conflicting instance variables
  aren't strict enough.  I think that sometimes two different classes
! adding __dict__ may be incompatible after all.
  
  Check for order conflicts.  Suppose there are two base classes X and
--- 2,28 ----
  ****************************
  
! Still to do (by priority)
! -------------------------
  
! Add __del__ handlers?  I asked for a motivation on python-dev and
! nobody piped up.  Yet I expect it will be asked for later.  Are there
! GC issues?  Doesn't the GC make an exception for classic classes with
! a __del__ handler?
  
  Support mixed multiple inheritance from classic and new-style classes?
+ That would be cool and make new-style classes much more usable (it
+ would remove most of the reasons not to use them for new projects).
+ How hard would this be?
  
+ Do something with the tp_cache slot?  This is (was?) intended to cache
+ all the class attributes from all base classes; a key would be deleted
+ when the base class attribute is.  But the question is, are the
+ savings worth it?  So I may not do this.
+ 
  Check for conflicts between base classes.  I fear that the rules used
  to decide whether multiple bases have conflicting instance variables
  aren't strict enough.  I think that sometimes two different classes
! adding __dict__ may be incompatible after all.  (I may not do this.
! Who cares.)
  
  Check for order conflicts.  Suppose there are two base classes X and
***************
*** 21,28 ****
  order should the base classes X and Y be searched?  This is an order
  conflict, and should be disallowed; currently the test for this is not
! implemented.
  
  Done (mostly)
  -------------
  
  More performance work -- one particular test, test_descr.inherits(),
--- 31,43 ----
  order should the base classes X and Y be searched?  This is an order
  conflict, and should be disallowed; currently the test for this is not
! implemented.  (I may not do this.  Who cares.)
  
+ Allow assignment to __bases__?  (I don't think there's a demand for
+ this.)
+ 
  Done (mostly)
  -------------
+ 
+ Assignment to __dict__.
  
  More performance work -- one particular test, test_descr.inherits(),