From: Leo S. M. <leo...@gm...> - 2008-07-23 15:00:03
|
Looks like the impact of realizing that I'm going to speak on DjangoCon[1] about Django/Jython made me forget some things, like continue with the weekly reports. Now I'm fixing this :) The first thing I did was change my workflow and organize my code as patch queues, which are better suited to follow and update the patches I submit to Django devs, and also my work in progress on the Jython side. The details, and short instructions to get the latest Django/Jython code is on <http://blog.leosoto.com/2008/07/my-new-djangojython-developer-workflow.html>. Note that I haven't be able to publish the results I'm getting from hudson, the continuous integration server I started to use. So I'll try to also update the ad-hoc status page[2] until I get some Java hosting space, maybe on Imagemaker's servers. On the last days most of the patches to Django needed for Jython integration has been commited, some of them after a bit of tweaking. The notable exception is #7560, but I'm confident that it will be eventually committed now that Django is on the road to 1.0-beta, and critical must-have features have been integrated to trunk. The great news is that the size of my patch queues have been greatly reduced, which means that shortly Django should run on top on Jython without any special patching :-) The not-so-good news is that I'm still chasing the test suite. Django moves really fast, and new failing tests cases arise from time to time. Anyway, looks like most failures are concentrated on Jython text-encoding handling, the new manage.py tests and some obscure remaining incompatibilities with CPython. So, we may have a ~15% failure rate, but a few critical fixes should kill most of the failures. Finally, here is some current work in progress: - sqlite3/zxJDBC backend. Jim Baker pointed me to the cool Zentus SQLiteJDBC driver[4], which includes a pure Java implementation. By now it doesn't work but it already served as a good practical example to extract code that should be reused by other zxJDBC drivers out of the PostgreSQL/zxJDBC backend. - modjy integration. Needs some final touches to modjy, like correctly setting SCRIPT_PATH. - WAR distribution. I have a proof-of-concept prototype, now going to rewrite and integrate it to Django, as a management command. And some important things which haven't be done yet but should to be addressed on the remaining GSoC weeks: - Reloading support for the dev server - Some kind of IDE integration - Documentation And a final note: on the past two weeks I managed to finish all my university exams, so now there is more time for the GSoC project :-) [1] http://djangocon.org [2] http://dojstatus.leosoto.com [3] http://code.djangoproject.com/ticket/7560 [4] http://www.zentus.com/sqlitejdbc/ -- Leo Soto M. http://blog.leosoto.com |