#36441: Add lazy loading support for GDAL library in `django.contrib.gis.gdal`
-------------------------------------+-------------------------------------
Reporter: Josh Thomas | Owner: Josh
Type: | Thomas
Cleanup/optimization | Status: assigned
Component: GIS | Version: dev
Severity: Normal | Resolution:
Keywords: gdal | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
I naively assumed importing gdal at the top of
`django.contrib.gis.db.models.fields` would raise an exception, but I
guess the point of that change is that it doesn't. So at what point would
an exception be raised? How does it compare to GEOS? Also consider that
it's possible to use aspects of GeoDjango that rely on GEOS and GDAL
without using the model fields.
I'm not sure if there's any reason to treat GEOS + GDAL differently. My
impression is that this is a new idea that Jacob had. If we do add it, the
check for both could be authored as a separate commit.
--
Ticket URL: <https://code.djangoproject.com/ticket/36441#comment:13>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199f47f29d3-3636bf57-ad2b-4e3c-b19c-027aff883d38-000000%40eu-central-1.amazonses.com.
