As part of the release of Jython 2.5 for later this year, the Jython developers have expressed the following goals:

    * Demonstrated suitability of Jython for running larger applications
    * Comprehensive testing of expected Python compatibility, including corner cases and customary if undocumented functionality in CPython
    * Enabling Python web app frameworks to effectively use Java technologies, such as threading, JDBC, servlet containers, WAR file distribution, IDE tools, JMX, and other functionality

Django is a large application framework that significantly exercises Python functionality. As part of this, Django employs comprehensive unit testing. As such, it is currently being used by the Jython, IronPython, and Python 3.0 projects to identify compatibility issues in their implementations. Lastly, Django running on Jython, like other Python web app frameworks, is a compelling alternative for Java developers who need to use the Java platform, but without unnecessary pain and development cost.

For my project for the Google Summer of Code, I propose to fill the gaps in running the current Django codebase on the Jython trunk (to be released as 2.5 in the future) and provide integration between the Django framework and common Java development tools. I plan to focus specifically on Django, as suggested by the Jython developers so that something concrete can be done over the summer, but the expectation is that this work should be generalizable to other web app frameworks too, including Pylons and TurboGears. This is why I'm applying to Jython/Python Software Foundation, as opposed to Django, for the Summer of Code.