Code

Opened 16 months ago

Closed 6 months ago

Last modified 6 months ago

#20052 closed Cleanup/optimization (fixed)

Running Django on Jython -- not supported at this time?

Reported by: adrien.sebbane@… Owned by: nobody
Component: Documentation Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

In the frame of the section, we can read:
"Django 1.5 has dropped support for Python 2.5. Therefore, you have to use a Jython 2.7"

This does not make sense because I think what was meant actually was "Jython 2.5".

Best Regards
Greetings

Adrien

Attachments (1)

20052.diff (3.5 KB) - added by timo 6 months ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 16 months ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted
  • Type changed from Uncategorized to Cleanup/optimization

Since Python and Jython versions are aligned, dropping support for Python 2.5 also drops support for Jython 2.5.

Let's revisit this note once Jython 2.7 final is released -- beta 1 was released one month ago.

Changed 6 months ago by timo

comment:2 Changed 6 months ago by timo

  • Has patch set
  • Summary changed from Running Django on Jython to Running Django on Jython -- not supported at this time?
  • Version changed from 1.5 to 1.4

It appears that django-jython hasn't been updated to work with a version of Django newer than 1.3. Since 1.3 is no longer supported, I suggest we discourage use of django-jython and remove the existing instructions. However, I'm not a user of django-jython so if anyone sees the situation differently, let me know. Draft patch attached.

comment:3 Changed 6 months ago by timo

  • Triage Stage changed from Accepted to Ready for checkin

I contacted the current maintainer of django-jython, Josh Juneau, and he said the proposed patch accurately reflects the state of the project.

comment:4 Changed 6 months ago by Tim Graham <timograham@…>

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

In a67e327db53f49aff374d5974b69de43da288bac:

Fixed #20052 -- Discouraged use of Jython given the current state of django-jython.

Thanks Josh Juneau (maintainer of django-jython) for the review.

comment:5 Changed 6 months ago by Tim Graham <timograham@…>

In b8ec3b6ddd835a66a239a4bdd5ee51b541ca09e4:

[1.6.x] Fixed #20052 -- Discouraged use of Jython given the current state of django-jython.

Thanks Josh Juneau (maintainer of django-jython) for the review.

Backport of a67e327db5 from master

comment:6 Changed 6 months ago by Tim Graham <timograham@…>

In f746d1fc74e5253b7c12484eab081818c8853b14:

[1.5.x] Fixed #20052 -- Discouraged use of Jython given the current state of django-jython.

Thanks Josh Juneau (maintainer of django-jython) for the review.

Backport of a67e327db5 from master

comment:7 Changed 6 months ago by Tim Graham <timograham@…>

In 1036e3ec7c7d7f99e3d9138e8f461c2cc690e03c:

[1.4.x] Fixed #20052 -- Discouraged use of Jython given the current state of django-jython.

Thanks Josh Juneau (maintainer of django-jython) for the review.

Backport of a67e327db5 from master

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.