|
Size: 451
Comment:
|
← Revision 6 as of 2009-10-28 10:13:14 ⇥
Size: 689
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| To Deprecate in 2.6 and Remove in 3.x ===================================== |
Ideas for backwards incompatible changes in 3.x =============================================== It would be good if most of these can have warnings in 2.6 |
| Line 9: | Line 10: |
| * Methods that do not take a ThreadState when there is a method that does (mainly in PyObject) * All of Py.java (It's a giant global that we should be able to split up -- maybe it will just become tiny) |
* In our core code kill methods that do not take a ThreadState when there is a method that does (mainly in PyObject) * Kill all of Py.java (It's a giant global that we should be able to split up -- maybe it will just become tiny) |
| Line 15: | Line 16: |
| * respectJavaAccessibility | * Kill respectJavaAccessibility |
| Line 21: | Line 22: |
Proxy generation ---------------- * Remove event properties -- they are arbitrary, hazardous and easy to go wrong with |
Ideas for backwards incompatible changes in 3.x
It would be good if most of these can have warnings in 2.6
Java
- In our core code kill methods that do not take a ThreadState when there is a method that does (mainly in PyObject)
- Kill all of Py.java (It's a giant global that we should be able to split up -- maybe it will just become tiny)
Registry
- Kill respectJavaAccessibility
Package Cache
- Disable by default, add an easy flag to enable.
Proxy generation
- Remove event properties -- they are arbitrary, hazardous and easy to go wrong with