1. On behalf of the Jython development team, I'm pleased to announce that
    Jython 2.2 is available for download. See the installation instructions.

    This is the first production release of Jython in nearly six years,
    and it contains many new features:
    • new-style classes
    • Java List integration
    • PEP 302 implementation
    • iterators
    • generators
    • __future__ division
    • support for running on modern JVMs
    • a new installer
    • ssl and non-blocking support for socket

    This gives Jython the same set of language features as Python 2.2.
    For a more complete list of the additions from 2.1 to 2.2, see the
    NEWS file in the release. Only the version numbers changed in the
    code from 2.2rc3 to this release.

    Woohoo!!
    Posted by
    Labels: jython
    13

    View comments

  2. I'll be giving a talk on Jython 2.2 and current Jython development on Tuesday, August 28, 7pm at 328 Phillips Hall, UNC-Chapel Hill in North Carolina for the Triangle Zope and Python Users Group. It will be a basic introduction to Jython targeted at Python developers, but since I learned my lesson at PyCon, I'll be sure to do more demoing.
    Posted by
    Labels: jython
    1

    View comments

  3. The Jython development team is pleased to announce that Jython 2.2rc3
    is available for download.

    Here are the installation instructions.

    A few new pieces of functionality have been added since 2.2rc2:

    • Added telnetlib from CPython
    • Added cpython_compatible_select to select. See here for information on when to use it.
    • Several more java.nio exceptions are mapped to their corresponding Python error codes when thrown.

    The following bugs are also fixed in this release:

    • recv on closed sockets threw an exception instead returning the empty string
    • A PySystemState being garbage collected caused System.out and System.in to be closed. This would cause 'print' to stop working.
    • Closing a FileWrapper on a socket closes its underlying socket
    • Sockets just have their [In|Out]putStreams closed instead of being properly shutdown by shutdown()
    • SO_REUSEADDR is reset on sockets from a server socket's accept call causing later binds to the server socket's port to fail.
    • Client sockets that have bind called before connect don't respect SO_REUSEADDR
    • execfile() throws a NullPointerException in the interactive console

    Enjoy!
    Posted by
    Labels: jython
    0

    Add a comment

About Me
About Me
Subscribe
Subscribe
Links
Links
Blog Archive
Blog Archive
Blog Roll
Blog Roll
Loading
Dynamic Views theme. Powered by Blogger. Report Abuse.