Opened 6 years ago

Closed 5 years ago

#20517 closed Bug (fixed)

Jython support is not as complete as indicated

Reported by: alex@… Owned by: Daniele Procida
Component: Documentation Version: master
Severity: Normal Keywords: Jython, afraid-to-commit
Cc: alex@… Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no


While django itself works admirably with Jython, there are a few issues not mentioned here which are likely to cause significant problems for people intending to rely on Jython to deploy Django.

For example, the django-jython database support packages don't work with versions above 1.3 without monkey patching, I believe.

Furthermore, due to some bugs or 'features' in Jython, many Django apps (including the Django Rest API) do NOT work with Jython at the moment. I wasted a couple of days figuring this out :( though to be fair, Django has saved me many more hours than that in my life :)

I believe the docs could be more informative here by providing a list of supported configurations and third-party apps.

For example:

Django does support Jython, but it can be a little finicky depending on what apps/versions you want to use.

Known good configurations:

  • Django 1.3.1 with Jython2.7b1 with django-jython1.3

Known to be incompatible:

  • Django 1.4+ with any version of django-jython (fixable with tiny patch - link).

Supported plug-ins:

Plug-ins known NOT to work:

  • Django REST framework

Installation instructions continue largely as before....

I know it may be difficult to generate such a list, but even an incomplete version listing a few major apps / working combinations would be very helpful in assessing whether or not this option is likely to work, potentially saving developers a lot of time and wasted effort!

Possibly it could even be done as a forum thread and linked to from the docs.

Change History (5)

comment:1 Changed 6 years ago by Luke Plant

Triage Stage: UnreviewedAccepted

This could be done as a wiki page, but we couldn't reasonably maintain a correct list of compatible/incompatible apps within Django docs itself, because out-of-date/incorrect information is just as unhelpful as no information at all. I'm going to accept the idea of having a warning and a link to such a wiki page within the docs though.

Care will still need to be taken with the wiki page - like putting sufficient dates and version numbers on the information.

comment:2 Changed 6 years ago by Daniele Procida

Owner: changed from nobody to Daniele Procida
Status: newassigned

I have marked this ticket as suitable for a first-time committer attending a Don't be afraid to commit workshop.

The next planned session will be hosted by Cardiff Dev Workshop on Saturday 8th June.

If you want to tackle this ticket before then, or at any time in fact, please don't let the fact that it's assigned to me stop you. Feel free to re-assign it to yourself and do whatever you like to it.

comment:3 Changed 5 years ago by Tim Graham

#19417 also notes an issue with Jython 2.5.3 and forms.DateTimeField which could be included with this.

comment:4 Changed 5 years ago by Daniele Procida

Keywords: afraid-to-commit added

I would like to reserve this ticket for first-time committers who take
part in the [ Don't be
afraid to commit tutorial] and the sprints at [
DjangoCon US 2013] in September.

However, if you want to tackle this ticket before then, please don't
hesitate. Feel free to re-assign it to yourself and do whatever you like
to it.

comment:5 Changed 5 years ago by Tim Graham

Resolution: fixed
Status: assignedclosed

I added the information in this ticket to the wiki page:

At this point I don't feel the page is complete enough to warrant a link from the official documentation, so I'm going to close this ticket. If the wiki page improves, we can reconsider.

Note: See TracTickets for help on using tickets.
Back to Top