Jython and Django 1.0
Leo Soto M.
Just wanted to make you know the status of Django on Jython given the
very cool features that have landed on trunk on the past weeks.
The news are very good -- if it weren't by my eagerness to remove code
duplication on the Postgresql/JDBC backend, Django should run
unpatched on Jython right now. Anyway, people can give it at try,
using the "asm" branch of Jython and the revision 2 of
django-jython[1]. When #5461 [2] lands, django-jython HEAD will work.
(BTW, I've updated the patch on #5461 a few minutes ago).
This means that no more outstanding changes to Django will be required
(like the get_db_prep_* one, or the signals reworking). What remains
is basically more bug-fixing (mostly on the Jython side) and some
integration work. For example, I've re-enabled isatty() on #8100 [3]
and made a jython-specific reloader for the development web server on
#8147 [4]. I hope that this mainly simple, but important change can
make it for 1.0-beta.
The single other open ticket related to Jython is #8047 [5], which is
related to the admin_script test. Naturally, I may open more tickets
as I go to bug-hunting mode on the following weeks, but that is. [Oh,
well, there is GeoDjango, but I think I'll defer that until Jython
gets ctypes support]
Finally, I want to make it clear that I'm not in any way complaining
about the open tickets -- quite the contrary, I'm amazed on how quick
and smooth have been the process.
So, kudos to all core developers for their help and support. This
community rocks!
[1] http://code.google.com/p/django-jython/
[2] http://code.djangoproject.com/ticket/5461
[3] http://code.djangoproject.com/ticket/8100
[4] http://code.djangoproject.com/ticket/8147
[5] http://code.djangoproject.com/ticket/8047
--
Leo Soto M.
http://blog.leosoto.com