1453
Comment:
|
2658
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
=== Jython 2.2 === | = Jython 2.2 = |
Line 5: | Line 5: |
==== Slots ==== | == regrtest Failures == |
Line 7: | Line 7: |
==== Bug Triage ==== | * descr * new * weakref * zlib * windows only failures |
Line 9: | Line 13: |
==== regrtest Failures ==== === Jython 2.3 === |
= Jython 2.3 = |
Line 34: | Line 36: |
PEP 218: A Standard Set Datatype | |
Line 35: | Line 38: |
==== Replace jythonc ==== | PEP 263: Defining Python Source Code Encodings |
Line 37: | Line 40: |
==== Solidify Import System ==== | PEP 273: Importing Modules from Zip Archives |
Line 39: | Line 42: |
==== Fix Java to Python naming integration ==== | PEP 278: Universal Newline Support |
Line 41: | Line 44: |
==== PEP 218: A Standard Set Datatype ==== | PEP 285: A Boolean Type |
Line 43: | Line 46: |
==== PEP 263: Defining Python Source Code Encodings ==== | PEP 305: Pickle Enhancements |
Line 45: | Line 48: |
==== PEP 273: Importing Modules from Zip Archives ==== | == Replace jythonc == |
Line 47: | Line 50: |
==== PEP 278: Universal Newline Support ==== | jythonc doesn't handle generators and is difficult to debug and improve. The current thinking is to add capabilites to jython itself to generate bytecode from py files and run those statically compiled items rather than jythonc's approach of making Java classes that work like the base Python code. See http://thread.gmane.org/gmane.comp.lang.jython.devel/1429/focus=1430 for the general idea. |
Line 49: | Line 52: |
==== PEP 285: A Boolean Type ==== | == Solidify Import System == |
Line 51: | Line 54: |
==== PEP 305: Pickle Enhancements ==== | Jython adds to Python's import system to handle loading from Java's classpath and to load from jar files. It's not exactly clear what modifications are in place and what techniques are best for adding jar files to the path at runtime and things like that. A JEP explaining what's been added and how things relate to both the Python and Jython sides would be nice. |
Line 53: | Line 56: |
=== Jython 2.4 === | == Complete Java to Python naming integration == Java allows a method and field of the same name to exist in the same class. Python only has a single namespace for these items. This leads to methods being hidden in a Java instance in Jython if the instance has a field of the same name. In addition, the bean convenience methods that map object.getField() in Java to object.field in Jython lead to collisions. A standard system for renaming fields and methods to avoid collisions and a JEP explaining the whole thing would be most welcome. = Jython 2.4 = |
Line 65: | Line 72: |
=== Jython 2.5 === | = Jython 2.5 = |
Contents TableOfContents
Jython 2.2
regrtest Failures
- descr
- new
- weakref
- zlib
- windows only failures
Jython 2.3
yield is always a keyword.
enumerate() built-in added.
int() will now return a long instead of raising OverflowError if a number is too large.
built-in types support extending slicing syntax.
list.insert() changed to be consistent with negative slice indexing.
list.index() takes optional start, stop arguments.
Dictionaries gained a pop() method and .fromkeys() class method.
dict() constructor takes keyword arguments.
assert no longer checks debug flag.
Many type objects are now callable.
PEP 218: A Standard Set Datatype
PEP 263: Defining Python Source Code Encodings
PEP 273: Importing Modules from Zip Archives
PEP 278: Universal Newline Support
PEP 285: A Boolean Type
PEP 305: Pickle Enhancements
Replace jythonc
jythonc doesn't handle generators and is difficult to debug and improve. The current thinking is to add capabilites to jython itself to generate bytecode from py files and run those statically compiled items rather than jythonc's approach of making Java classes that work like the base Python code. See http://thread.gmane.org/gmane.comp.lang.jython.devel/1429/focus=1430 for the general idea.
Solidify Import System
Jython adds to Python's import system to handle loading from Java's classpath and to load from jar files. It's not exactly clear what modifications are in place and what techniques are best for adding jar files to the path at runtime and things like that. A JEP explaining what's been added and how things relate to both the Python and Jython sides would be nice.
Complete Java to Python naming integration
Java allows a method and field of the same name to exist in the same class. Python only has a single namespace for these items. This leads to methods being hidden in a Java instance in Jython if the instance has a field of the same name. In addition, the bean convenience methods that map object.getField() in Java to object.field in Jython lead to collisions. A standard system for renaming fields and methods to avoid collisions and a JEP explaining the whole thing would be most welcome.
Jython 2.4
Built-in set, frozenset
Unifying int/long
Generator expressions
Function/method decorators
Multi-line imports
Jython 2.5
Conditional expressions
'with' statement
Absolute & relative imports
Unified try/except/finally
New generator features
Exceptions as new-style classes
The index method