[Django] #30679: Warn when Djasngo works with unsupported version of GDAL

3 views
Skip to first unread message

Django

unread,
Aug 5, 2019, 4:35:23 AM8/5/19
to django-...@googlegroups.com
#30679: Warn when Djasngo works with unsupported version of GDAL
---------------------------------------+------------------------
Reporter: Yury Ryabov | Owner: nobody
Type: New feature | Status: new
Component: GIS | Version: 2.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+------------------------
When Django is paired with an unsupported version of GDAL, same common
geospatial operation may result in an OGR error (and it is OK cause in
this case the issue is easily traceable) or in incorrect result. When
there is an incorrect result it is much harder to spot the issue and it
takes great deal of time to get to the root of it (which is an unsupported
GDAL version). [https://code.djangoproject.com/ticket/30645 The example is
here].

It will be nice to have a built-in check at the start of the Django
(server, tests, migrations, etc.) that will warn developers about
unsupported version of GDAL being used.

--
Ticket URL: <https://code.djangoproject.com/ticket/30679>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Aug 5, 2019, 5:27:55 AM8/5/19
to django-...@googlegroups.com
#30679: Warn when Django works with unsupported version of GDAL.
-------------------------------------+-------------------------------------

Reporter: Yury Ryabov | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: GIS | Version: master
Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):

* status: new => closed
* resolution: => wontfix
* version: 2.2 => master
* type: New feature => Cleanup/optimization


Comment:

Thanks for the ticket, however I don't think that a warning or a hard
restriction for not confirmed versions of `GDAL` is required. It is
documented and `GDAL` 3.0+ can work properly even if it's not confirm by
Django, users can use them on their own risk. All of such checks restricts
the oldest supported versions.

--
Ticket URL: <https://code.djangoproject.com/ticket/30679#comment:1>

Reply all
Reply to author
Forward
0 new messages