diff options
author | Guido van Rossum <guido@python.org> | 2001-09-28 18:19:21 (GMT) |
---|---|---|
committer | Guido van Rossum <guido@python.org> | 2001-09-28 18:19:21 (GMT) |
commit | 43b9a086bf6b01c2746e2d0289e92c508fcfa72e (patch) | |
tree | 98bd08a21a10374759a9aac4babeaf4f140d2f12 /PLAN.txt | |
parent | 8b9def3aacd4b23797d58341e39a431ef128fc69 (diff) | |
download | cpython-43b9a086bf6b01c2746e2d0289e92c508fcfa72e.zip cpython-43b9a086bf6b01c2746e2d0289e92c508fcfa72e.tar.gz cpython-43b9a086bf6b01c2746e2d0289e92c508fcfa72e.tar.bz2 |
Reorder Still To Do items (highest priority on top), add one.
Diffstat (limited to 'PLAN.txt')
-rw-r--r-- | PLAN.txt | 26 |
1 files changed, 14 insertions, 12 deletions
@@ -4,6 +4,20 @@ Project: core implementation Still to do ----------- +Treat all binary operators the same way as I just did for rich +comparison: in a <op> b, if isinstance(b, type(a)), try b.__rop__(a) +before trying a.__op__(b). + +Make __dynamic__ the default (this requires more performance work -- +one particular test, test_descr.inherits(), is about 10x slower when +__dynamic__ is 1. :-( + +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 @@ -16,18 +30,6 @@ 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. -Allow assignment to __bases__ and __dict__? - -Make __dynamic__ the default. - -Add __del__ handlers. - -Add __coerce__? - -Support pickling (via __reduce__) - -Support mixed multiple inheritance from classic and new-style classes? - Done (mostly) ------------- |