---------- Forwarded message ----------
From: Leo Soto M. <[EMAIL PROTECTED]>
Date: Sun, Jun 15, 2008 at 11:25 PM
Subject: GSoC Weekly Report (#3): Django on Jython
To: JythonDevelopers <[EMAIL PROTECTED]>
So, I'm a bit late with the weekly report. in part because it has been
a stressful week. Excuses apart, here is what was done in the last
week. The goal was fixing the remaining test failures, and here is
what I did:
- Wrote XML and JSON doctest output checkers, to avoid spurious
failures caused by differences on the ordering of attributes.
- Solved PyDispatcher test failures -- they were caused by the
different way in which the Jython GC works.
- Solved remaining issues with Jython string interpolation when
unicode arguments were present.
- Solved problems with DecimalField and zxJDBC.
- Improved date, time and datetime type conversion between Java and Python.
- tzinfo implementation backed by java.util.TimeZone.
Ironically, I had around 25 failures at the start of the week, and,
after the fixes listed above, I have the same number now. Part of the
reason is that one test (forms) was not being previously ran because
it contained a giant doctest which Jython refused to load. The other
part is that the majority of the tests are very sequential, so fixing
a failure often means discovering another one (for example, the zxJDBC
problems with Decimal were unnoticed the previous week).
So, here is a breakdown of the current problems [1], detailing the
issues which must be solved and how many tests are failing because of
them:
1. *Derived __getattr__ swallows custom AttributeErrors raised from descriptors
(#1041): basic(1)
2. (Apparently on zxJDBC): We have some zeros and ones instead of
False and True: model_inheritance_regress(1)
3. Duplicated keys on PgSQL raises SQLException instead of IntegrityError:
one_to_one(1)
4. Issues with Django's _decimal.py __cmp__: forms(1)
5. Remaining problems with Model.save(saw=True) and JDBC data types:
serializers_regress(3?).
6. Unordered list of Django's newforms validation errors: forms(1)
7. i18n (gettext?) Issues: forms(1), i18n(2)
8. Incomplete strptime: forms(2)
9. repr(float(0.1)) != '0.10000000000000001': i18n(1)
10. Lack of unicodedata: defaultfilters(1)
11. re and Unicode problems (#1046): views(1)
12. Lack of source encoding support (PEP 263): str(1), serializers(1),
string_lookup(1), forms(7)
I'm currently working on a good fix for (1) -- I previously wrote
another but wasn't happy with it. (2), (3) and (4) shouldn't pose
great problems as far as I've seen. As discussed previously, (11) and
(12) should go away when the asm branch is merged to trunk, and (10)
should wait a bit more. Finally, (5) worries me a bit because it is
blocking the patch I plan to submit to Django with the small refactor
of some django.db.models.get_db_prep_* methods.
I've not given too much thought at most of the other "new" points yet.
I will discuss this a bit more with Jim before planning the following
week(s).
[1] http://dojstatus.leosoto.com/testcollector/32/
--
Leo Soto M.
http://blog.leosoto.com
--
Leo Soto M.
http://blog.leosoto.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
