Differences between revisions 1 and 4 (spanning 3 versions)

Ideas for backwards incompatible changes in 3.x

It would be good if most of these can have warnings in 2.6

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)

-  ⇤ ← Revision 1 as of 2009-10-09 13:17:29 → 
  Size: 366
  Editor: FrankWierzbicki
  Comment:
+   ← Revision 4 as of 2009-10-22 20:11:24 → ⇥
  Size: 558
  Editor: FrankWierzbicki
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 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 16:
+Line 17:
+Package Cache
-------------

* Disable by default, add an easy flag to enable.

Diff for "Jython3000"