#28237: Allow GDAL library detection to work with non "dot zero" releases
--------------------------------------+------------------------------------
Reporter: Adam Starrh | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: GIS | Version: 1.11
Severity: Normal | Resolution:
Keywords: GIS, OSGeo4Win | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Adam Starrh):
Actually,
It looks to me like the .dll filenames only seem to change with major
releases.
I think
{{{"gdal111", "gdal110", "gdal19", "gdal18", "gdal17"}}}
are versions: **1.7**, **1.8**, **1.9**, **1.10** and **1.11**
If this is the case, then it's likely that
{{{"gdal201", "gdal202"}}
are versions: **2.1** and **2.2** with leading zeroes now included.
Given that 2.1 and 2.2 are versions that have been released, its unlikely
that I am getting 2.0.1 and 2.0.2 dlls in my download.
--
Ticket URL: <https://code.djangoproject.com/ticket/28237#comment:12>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.5384ce7d1b5f8e5e64fb7366114acc40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.