Differences between revisions 50 and 51
Revision 50 as of 2012-06-02 22:21:44
Size: 1428
Editor: 112
Comment:
Revision 51 as of 2012-09-01 09:19:57
Size: 2380
Editor: JeffAllen
Comment: wiki restore 2013-01-23
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:

= Jython Roadmap =
Line 3: Line 5:
2.6.0
=====
== Position Now ==
Line 6: Line 7:
 * Upgrade to Python 2.6 language and builtins, along with a substantial subset of the stdlib
 * Redesign PySystemState, ThreadState API
 * Mark true-public APIs with a suitable annotation; deprecate and/or remove obsolete APIs
 * Remove all user-visible singletons in org.python.core, especially any static public fields (like those in PySystemState)
 * Performance!
 * Require minimum Java 6, rip out Java 5 compatibility:
Line 13: Line 8:
  * Generic.newSetFromMap
  * Believe we can remove the xercesImpl jar, livetribe-jsr223-2.0.5.jar
  * can start utilizing jsr199 (the Java compiler API) for certain things (mostly for unittests I believe)
  * Other things..
(Least edited 1 September 2012.)
Line 18: Line 10:
Who is doing what?
==================

 * v2.5.3 is current.


== Current Plan ==


(Least edited 1 September 2012: Needs more detail.)


 * v2.5.x versions may appear consolidating bug-fixes
 * v2.6 is skipped
 * v2.7 is the main focus of current work. A beta is imminent (September 2012).
 * v3.x (3.3 probably) is under consideration.


== Who is doing what? ==


 * [[http://bugs.jython.org|Bug fixes]]: anyone


=== Towards v2.7 ===
Line 26: Line 40:
 * `bytearray`, buffer API and a partial `memoryview`: Jeff
Line 27: Line 42:
2.6.? (TBD)
===========

=== Towards v3.3 ===


 * Use of Java 7 `invokedynamic`: Jim?


== Scraps of former plans ==


When the page bore a roadmap was for v2.6, this material was in it. Some of it is still accurate for v2.7, some is probably complete now, and some is no longer relevant. Those who know which is which are able to improve the roadmap!


=== 2.6.0 ===


 * Upgrade to Python 2.6 language and builtins, along with a substantial subset of the stdlib
 * Redesign [[PySystemState|PySystemState]], [[ThreadState|ThreadState]] API
 * Mark true-public APIs with a suitable annotation; deprecate and/or remove obsolete APIs
 * Remove all user-visible singletons in org.python.core, especially any static public fields (like those in `PySystemState`)
 * Performance!
 * Require minimum Java 6, rip out Java 5 compatibility:
  * Generic.newSetFromMap
  * Believe we can remove the xercesImpl jar, livetribe-jsr223-2.0.5.jar
  * can start utilizing jsr199 (the Java compiler API) for certain things (mostly for unittests I believe)
  * Other things..



=== 2.6.? (TBD) ===
Line 33: Line 77:
 * ReplaceJythonc
 * MigrateBugtests
 * [[ReplaceJythonc|ReplaceJythonc]]
 * [[MigrateBugtests|MigrateBugtests]]
Line 38: Line 82:
Future?
=======

===
Future? ===

Jython Roadmap

Position Now

(Least edited 1 September 2012.)

  • v2.5.3 is current.

Current Plan

(Least edited 1 September 2012: Needs more detail.)

  • v2.5.x versions may appear consolidating bug-fixes
  • v2.6 is skipped
  • v2.7 is the main focus of current work. A beta is imminent (September 2012).
  • v3.x (3.3 probably) is under consideration.

Who is doing what?

Towards v2.7

  • math module: Oti
  • documentation, text_xrange.py, test_complex.py: Josh
  • grammar cleanup, test_class.py: Frank
  • itertools, collections: Jim
  • mercurial move, abcs, exceptions, posix/ntpath, io, tarfile: pjenvey
  • bytearray, buffer API and a partial memoryview: Jeff

Towards v3.3

  • Use of Java 7 invokedynamic: Jim?

Scraps of former plans

When the page bore a roadmap was for v2.6, this material was in it. Some of it is still accurate for v2.7, some is probably complete now, and some is no longer relevant. Those who know which is which are able to improve the roadmap!

2.6.0

  • Upgrade to Python 2.6 language and builtins, along with a substantial subset of the stdlib
  • Redesign PySystemState, ThreadState API

  • Mark true-public APIs with a suitable annotation; deprecate and/or remove obsolete APIs
  • Remove all user-visible singletons in org.python.core, especially any static public fields (like those in PySystemState)

  • Performance!
  • Require minimum Java 6, rip out Java 5 compatibility:
    • Generic.newSetFromMap
    • Believe we can remove the xercesImpl jar, livetribe-jsr223-2.0.5.jar
    • can start utilizing jsr199 (the Java compiler API) for certain things (mostly for unittests I believe)
    • Other things..

2.6.? (TBD)

Future?

  • ctypes module

  • Translate summer of code compiler to Java *Incorporated, except for pyc support

RoadMap (last edited 2013-02-06 23:22:57 by FrankWierzbicki)