#30678: Confirm support for GDAL 3.0.
--------------------------------------+------------------------------------
     Reporter:  Yury Ryabov           |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  GIS                   |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:  GDAL, GIS             |             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):

 This still doesn't seem to be working for me. The latest version of Django
 that I get from pip (2.2.6) does not contain `gdal204` in the `libgdal.py`
 file as indicated in the above comment (which seems to link to code for
 the Django 3 beta).  Furthermore, if I add it manually,
 [https://code.djangoproject.com/ticket/28237 which worked last time], it
 still doesn't solve the issue. If I set `GDAL_LIBRARY_PATH` to the .dll
 directly, I get: `OSError: [WinError 126] The specified module could not
 be found.`

 Is this working on other Windows systems with the latest version of
 OSGeo4Win? As it stands, following the directions in the GeoDjango docs
 isn't resulting in a successful installation for me.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30678#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.669b0aded58856d13c7dc4b21997ed50%40djangoproject.com.

Reply via email to