Python Web Framework on the JVM

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

Python, a dynamic object-oriented programming language, has been around for quite some time. In its lifetime there have been many web frameworks to choose from (i.e. Pylons, TurboGears, CherryPy, Zope, Django, etc) making it difficult for developers to make a selection as Ian Bicking pointed out,

For a long, long time (longer than most of those frameworks have existed) people have complained about the proliferation of web frameworks in Python.

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Developed and used over two years by a fast-moving online-news operation, Django was designed to handle two challenges: the intensive deadlines of a newsroom and the stringent requirements of the experienced Web developers who wrote it. It lets you build high-performing, elegant Web applications quickly.

Django focuses on automating as much as possible and adhering to the DRY principle.

An implementation of the high-level, dynamic, object-oriented language Python written in 100% Pure Java, and seamlessly integrated with the Java platform. It thus allows you to run Python on any Java platform.

It took nearly 6 years for Jython to go from version 2.1 to 2.2, but in just the last few months Jython has gone through two release candidates and another stable release, currently at 2.2.1. The Jython developers are working hard on producing Jython 2.5 which aims to align Jython with CPython 2.5 and provide a much cleaner and consistent code base.

A side goal of Jython 2.5 is to try to get some CPython frameworks working, especially the web frameworks, for example:

Django

Pylons

TurboGears

Twisted

InfoQ recently had the opportunity to interview Jim Baker, a python evangelist and contributor to Django on Jython (DoJ), to find out what is expected and when.

What is the expected release date for Django on Jython?

This year. It's predicated on the next release of Jython. See #2 for that planning. Django in contrast just works, with only minor changes, thanks to a lot of work that many other people did in identifying (minor) Jython incompatibilities. Now most of the problems we have identified actually occur only in testing, where Django makes certain assumptions about Python should run that don't apply to Jython. An example of such an assumption that the hash algorithm is the same for dictionary implementations; because we use Java's (ConcurrentHashMap), this is not the case. However, that's an artifact of the testing process, Django doesn't really care about that. Still, we plan to certify this by passing all the tests (fixed as necessary).

What version of Jython is going to be required?

Jython 2.5 - equivalent to CPython 2.5 (or what is conventionally called Python!) is what we are targeting in the Jython project. This is actually moving very fast. We have a 2.5 compiler that's available for experimental usage, but it's getting more and more robust as we have additional people testing it. This "newcompiler" was initiated by a Google Summer of Code project that I mentored. (Bruce Eckel mentioned this in a blog post. We in fact hit that mid-September date!) At the Python Conference in mid-March, we will be setting the specific target based on where we are. Tobias and I will also be presenting our paper "A New Compiler for Jython" at PyCon.

With the release, will there be a simpler install? Currently your blog post suggests applying patches, copying files, etc.

There will be a simple install! My reporting was simply to show how close we were in fact to this goal. I also anticipate plugin support in major IDEs like Eclipse or Netbeans, although this will come later.

Is Django trying to be what Rails is for Ruby and Grails is becoming for Groovy?

Django offers comparable functionality to those web app frameworks, with ostensibly a more robust platform. So Django is written to be multithreaded, unlike RoR, which means we don't have to go through a lot of tricks to make it work on the Java platform, such as using multiple classloaders. We currently have database support for PostgreSQL, with some work done also on MySQL. I helped write the Oracle backend for Django. We're also planning to support Java DB (Derby).

Jim also expressed the usefulness of having a preconfigured stack available, to ease the experimentation of using Django on Jython (DoJ),

I'd like to see the following preconfigured stack available for Django on Jython (DoJ): Derby + Tomcat. This should be something that a developer can just access via a plugin from Eclipse or Netbeans or IDE of their choice, which means they can configure Derby and Tomcat directly from the IDE. It also provides an obvious migration path to other containers and databases. Perhaps more importantly, such a setup allows for easy DoJ experimentation, whether that's for someone building a Django app, or also using tuple spaces, rules engines, PDF tools, or other parts of the heavy-lifting infrastructure available on the Java platform. This is where I think DoJ provides true compelling value.

Good to see the Jython project moving again! Sun lost an opportunity when Microsoft hired Jim Hugunin, Jython's creator and lead developer, to lead the IronPython project.

Django is often contrasted with Ruby on Rails, both frameworks having started around roughly the same time and sharing many of the same philosophies and goals. The JVM ports of the two frameworks highlight one of the key differences between the two framework code bases though, as "Rails uses every metaprogramming trick in the book" while the Jython developers chose Django as their first framework to attempt to run on Jython 2.5 as it's coding style is much less magical.

One of the benefits of using a framework is that key parts can be written in a system level langauge such as C, Java or C#. Unfortunately, as soon as you do this you loose the ability to easily run on different platforms. Python frameworks Zope and Grok for example have large portions written in C, which means that while it can be compiled for different platforms, it can't participate in the CLR or the JVM worlds. Likewise frameworks such as Ruby on Rails or Django are less likely to maintain key parts of the framework in Java since they will have users that want to deploy on CRuby or CPython. You can have alternative implementations in your native language but it places a significant maintenance burden on the framework authors.

Congratulations InfoQ - at last an article covering Python and Jython. Being a regular reader to your site I was under the impression that there is only Java and Ruby in the world :-)

It is good to see that even without Sun's help Jython is moving forward and soon we will be able to run Django on the JVM. This is really exciting news for a developer like me who using both Java and Python on a production system.

Good to see the Jython project moving again! Sun lost an opportunity when Microsoft hired Jim Hugunin, Jython's creator and lead developer, to lead the IronPython project.

To be fair to Sun, it felt like Jython stagnated long before the IronPython move. It might have just been 'before its time' -- people were less interested in dynamic languages on the JVM in Jython's heyday, and by the time they were, it was outdated.

It is also my understanding (though I don't have time to hunt down my source), that Sun fully intends to support a number of dynamic languages on the JVM. If memory, serves, they selected Ruby (much to my chagrin :) for a couple of reasons: momentum and you have to pick SOMEWHERE to start. See point #1. I imagine Python should soon see some love from Sun, but, obivously, doesn't strictly *need* it.

Is your profile up-to-date? Please take a moment to review and update.

Email Address

Note: If updating/changing your email, a validation request will be sent

Company name:

Keep current company name

Update Company name to:

Company role:

Keep current company role

Update company role to:

Company size:

Keep current company Size

Update company size to:

Country/Zone:

Keep current country/zone

Update country/zone to:

State/Province/Region:

Keep current state/province/region

Update state/province/region to:

Subscribe to our newsletter?

Subscribe to our architect newsletter?

Subscribe to our industry email notices?

You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.

We notice you're using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.