Code

#20517 closed Bug (fixed)

Jython support is not as complete as indicated

Reported by: alex@… Owned by: EvilDMP
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

Description

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.

Attachments (0)

Change History (5)

comment:1 Changed 14 months ago by lukeplant

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

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 14 months ago by EvilDMP

  • Owner changed from nobody to EvilDMP
  • Status changed from new to assigned

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 12 months ago by timo

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

comment:4 Changed 10 months ago by EvilDMP

  • Keywords Jython, afraid-to-commit added; Jython removed

I would like to reserve this ticket for first-time committers who take
part in the [http://www.djangocon.us/schedule/presentation/7/ Don't be
afraid to commit tutorial] and the sprints at [http://djangocon.us/
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 10 months ago by timo

  • Resolution set to fixed
  • Status changed from assigned to closed

I added the information in this ticket to the wiki page: https://code.djangoproject.com/wiki/DjangoAndJython

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.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.