Differences between revisions 7 and 8
Revision 7 as of 2006-11-24 22:04:48
Size: 2686
Comment:
Revision 8 as of 2006-11-24 22:35:45
Size: 3230
Editor: KhalidZuberi
Comment: mark a few things as done, add some reference links
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
yield is always a keyword. yield is always a keyword. '''[done]'''
Line 22: Line 22:
dict() constructor takes keyword arguments. dict() constructor takes keyword arguments. '''[done. also applied in 2.2]'''
Line 30: Line 30:
PEP 218: A Standard Set Datatype [http://www.python.org/dev/peps/pep-0218/ PEP 218]: A Standard Set Datatype
Line 32: Line 32:
PEP 263: Defining Python Source Code Encodings [http://www.python.org/dev/peps/pep-0263 PEP 263]: Defining Python Source Code Encodings
Line 34: Line 34:
PEP 273: Importing Modules from Zip Archives [http://www.python.org/dev/peps/pep-0273 PEP 273]: Importing Modules from Zip Archives
Line 36: Line 36:
PEP 278: Universal Newline Support [http://www.python.org/dev/peps/pep-0278 PEP 278]: Universal Newline Support
Line 38: Line 38:
PEP 285: A Boolean Type [http://www.python.org/dev/peps/pep-0285 PEP 285]: A Boolean Type
Line 40: Line 40:
PEP 305: Pickle Enhancements [http://www.python.org/dev/peps/pep-0395 PEP 305]: Pickle Enhancements

Reference: [http://www.python.org/doc/2.3/whatsnew/ Whats New in Python 2.3]
Line 53: Line 55:


Reference: [http://www.python.org/doc/2.4/whatsnew/ Whats New in Python 2.4]
Line 70: Line 75:

Reference: [http://www.python.org/doc/2.5/whatsnew/ Whats New in Python 2.5]

Contents TableOfContents

Jython 2.3

Builtins

yield is always a keyword. [done]

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. [done. also applied in 2.2]

assert no longer checks debug flag.

Many type objects are now callable.

PEPs

[http://www.python.org/dev/peps/pep-0218/ PEP 218]: A Standard Set Datatype

[http://www.python.org/dev/peps/pep-0263 PEP 263]: Defining Python Source Code Encodings

[http://www.python.org/dev/peps/pep-0273 PEP 273]: Importing Modules from Zip Archives

[http://www.python.org/dev/peps/pep-0278 PEP 278]: Universal Newline Support

[http://www.python.org/dev/peps/pep-0285 PEP 285]: A Boolean Type

[http://www.python.org/dev/peps/pep-0395 PEP 305]: Pickle Enhancements

Reference: [http://www.python.org/doc/2.3/whatsnew/ Whats New in Python 2.3]

Jython 2.4

Built-in set, frozenset

Unifying int/long

Generator expressions

Function/method decorators

Multi-line imports

Reference: [http://www.python.org/doc/2.4/whatsnew/ Whats New in Python 2.4]

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

Reference: [http://www.python.org/doc/2.5/whatsnew/ Whats New in Python 2.5]

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. An informational 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. See http://thread.gmane.org/gmane.comp.lang.jython.user/4919/ and http://jython.org/bugs/1509095. A standard system for renaming fields and methods to avoid collisions and a JEP explaining the whole thing would be most welcome.

BiggerTasks (last edited 2008-11-15 09:16:00 by localhost)