--
Ticket URL: <https://code.djangoproject.com/ticket/24499>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/4345 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:1>
Comment (by claudep):
I'm not so enthusiast about dropping it now. It's still in use by many
stable distros, hopefully not any longer when 1.9 will be released, but
still... What about dropping it in Django 2.0?
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:2>
Comment (by timgraham):
If you think it's still providing value, I'm not in a rush, but I raised
the issue because Daniel said his
[https://github.com/django/django/pull/4339 raster work] requires PostGIS
2.0. We'll just have to add a feature flag for that.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:3>
* keywords: => 2.0
* needs_better_patch: 0 => 1
* stage: Unreviewed => Someday/Maybe
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:4>
Comment (by claudep):
You could ask on the Geodjango ML if withdrawal of PostGIS 1.5 from Django
1.9 would hurt anyone.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:5>
* needs_better_patch: 1 => 0
Comment:
[https://groups.google.com/d/topic/geodjango/E2ZWIKeq24c/discussion No
replies in 7 days] although the post has 7 views according to Google
groups. Should we try any harder to get feedback? I think we should be
somewhat free to drop older technologies, particularly since 1.8 is LTS.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:6>
Comment (by claudep):
We are talking about dropping it for 1.9, not 1.8, right? I would be
strongly -1 to drop it in 1.8.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:7>
Comment (by aaugustin):
Yes, we're talking about dropping it from 1.9. The impact on users is
lessened because 1.8 is LTS.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:8>
Comment (by claudep):
Ah, sorry. I misunderstood the comment.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:9>
* keywords: 2.0 =>
* stage: Someday/Maybe => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:10>
* stage: Accepted => Ready for checkin
Comment:
Patch looks good per Claude, but I'm going to try to put together
something like a docker config to ease testing on newer versions of
PostGIS since Claude's system (Debian stable) includes 1.5 and he is our
main contributor.
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:11>
Comment (by claudep):
Thanks /o\
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:12>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"26996e2d55719deb0a0b85c642c88658c929106c" 26996e2d]:
{{{
#!CommitTicketReference repository=""
revision="26996e2d55719deb0a0b85c642c88658c929106c"
Fixed #24499 -- Dropped support for PostGIS 1.5.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:13>
Comment (by Tim Graham <timograham@…>):
In [changeset:"ab873e7a681e62d6803a3c04a051a47335f7b93a" ab873e7]:
{{{
#!CommitTicketReference repository=""
revision="ab873e7a681e62d6803a3c04a051a47335f7b93a"
Refs #24499 -- Removed an obsolete test check for PostGIS 1.5.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:14>
Comment (by Tim Graham <timograham@…>):
In [changeset:"703369fb25ad0cc8db844127085a3ae76260dab3" 703369f]:
{{{
#!CommitTicketReference repository=""
revision="703369fb25ad0cc8db844127085a3ae76260dab3"
[1.9.x] Refs #24499 -- Removed an obsolete test check for PostGIS 1.5.
Backport of ab873e7a681e62d6803a3c04a051a47335f7b93a from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24499#comment:15>