Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#21244 closed Bug (duplicate)

GIS Version Regex on Mac OSX

Reported by: pyrospade Owned by: nobody
Component: GIS Version: 1.4
Severity: Normal Keywords: GIS OSX
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

On Mac OSX, when using GIS the version regex fails to parse the trailing rXXXX number. I have submitted a pull request here with the changes -

https://github.com/django/django/pull/1709

Change History (6)

comment:1 Changed 3 years ago by Claude Paroz

Resolution: duplicate
Status: newclosed

This is fixed in Django 1.5. See also #20036.

comment:2 Changed 3 years ago by pyrospade

Resolution: duplicate
Status: closednew

Requesting to re-open. I currently have projects that use Django 1.4. Is there any way that we can merge my changes into the stable/1.4.x branch?

Last edited 3 years ago by pyrospade (previous) (diff)

comment:3 Changed 3 years ago by Marc Tamlyn

Resolution: duplicate
Status: newclosed

No, bug fixes are not back ported that far, even for LTS releases. Only security patches. See the support life cycle docs - https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions

comment:4 Changed 3 years ago by pyrospade

This is unfortunate. I see several commits and pull requests merged this month that are unrelated to security in any way. This is an actual bug that is affecting developers.

comment:5 Changed 3 years ago by Marc Tamlyn

Er, there are no commits on stable/1.4 this month, and all the commits made in September are relating to security fixes and releases. As Claude stated, this is fixed in 1.5. It is important that old versions have as few changes as possible so as not to break running applications. If it is causing significant pain, I suggest updating the projects to 1.5.

comment:6 Changed 3 years ago by pyrospade

Understood. I can update my requirements to use my fork instead; however, I thought the community may benefit from the fix I proposed.

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