Opened 5 years ago
Closed 5 years ago
#30679 closed Cleanup/optimization (wontfix)
Warn when Django works with unsupported version of GDAL.
| Reported by: | Yury Ryabov | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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). 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.
Change History (1)
comment:1 by , 5 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
| Summary: | Warn when Djasngo works with unsupported version of GDAL → Warn when Django works with unsupported version of GDAL. |
| Type: | New feature → Cleanup/optimization |
| Version: | 2.2 → master |
Note:
See TracTickets
for help on using tickets.
Thanks for the ticket, however I don't think that a warning or a hard restriction for not confirmed versions of
GDALis required. It is documented andGDAL3.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.