It's probably better to advise checking the Library Path before setting it
to the project settings file, maybe as a last resort. For many MacOS
homebrew users, the library might be not installed in the default library
PATH (for instance, homebrew installs it to /opt/homebrew/lib/), non
visible Library paths in default environment is I think relative common.
My advise is to print "... If it is, try checking your environment library
path or try setting GDAL_LIBRARY_PATH in your settings.'
--
Ticket URL: <https://code.djangoproject.com/ticket/34375>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Old description:
> Currently the error message for GDAL and GIS when not locating the
> required library is:
> '''Could not find the GDAL library (tried "%s"). Is GDAL installed? If it
> is, try setting GDAL_LIBRARY_PATH in your settings.'''
>
> It's probably better to advise checking the Library Path before setting
> it to the project settings file, maybe as a last resort. For many MacOS
> homebrew users, the library might be not installed in the default library
> PATH (for instance, homebrew installs it to /opt/homebrew/lib/), non
> visible Library paths in default environment is I think relative common.
>
> My advise is to print "... If it is, try checking your environment
> library path or try setting GDAL_LIBRARY_PATH in your settings.'
New description:
Currently the error message for GDAL and GIS when not locating the
required library is:
'''Could not find the GDAL library (tried "%s"). Is GDAL installed? If it
is, try setting GDAL_LIBRARY_PATH in your settings.'''
It's probably better to advise checking the Library Path before setting it
to the project settings file, maybe as a last resort. For many MacOS
homebrew users, the library might be not installed in the default library
PATH (for instance, homebrew installs it to /opt/homebrew/lib/), non
visible Library paths in default environment is I think relative common.
My advise is to print "... If it is, try checking your environment library
path or try setting GDAL_LIBRARY_PATH in your settings."
--
--
Ticket URL: <https://code.djangoproject.com/ticket/34375#comment:1>
* owner: (none) => Julia Singh
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/34375#comment:2>
* status: assigned => closed
* resolution: => invalid
Comment:
> non visible Library paths in default environment is I think relative
common.
Yes, however I don't think we should advise changing library paths for
every custom library. Folks who know how to do it and want to do it will
do this anyway.This is not something that Django should advise as it's not
directly related with Django. Adding `GDAL_LIBRARY_PATH` to the settings
is Django's way of fixing this.
--
Ticket URL: <https://code.djangoproject.com/ticket/34375#comment:3>
* component: contrib.postgres => GIS
--
Ticket URL: <https://code.djangoproject.com/ticket/34375#comment:4>
Old description:
> Currently the error message for GDAL and GIS when not locating the
> required library is:
> '''Could not find the GDAL library (tried "%s"). Is GDAL installed? If it
> is, try setting GDAL_LIBRARY_PATH in your settings.'''
>
> It's probably better to advise checking the Library Path before setting
> it to the project settings file, maybe as a last resort. For many MacOS
> homebrew users, the library might be not installed in the default library
> PATH (for instance, homebrew installs it to /opt/homebrew/lib/), non
> visible Library paths in default environment is I think relative common.
>
> My advise is to print "... If it is, try checking your environment
> library path or try setting GDAL_LIBRARY_PATH in your settings."
New description:
Currently the error message for GDAL and GIS when not locating the
required library is:
'''Could not find the GDAL library (tried "%s"). Is GDAL installed? If it
is, try setting GDAL_LIBRARY_PATH in your settings.'''
It's probably better to advise checking the Library Path before setting it
to the project settings file, maybe as a last resort. For many MacOS
homebrew users, the library might be not installed in the default library
PATH (for instance, homebrew installs it to /opt/homebrew/lib/), non
visible library paths in default environment is I think relatively common.
My advise is to print "... If it is, check your environment library path
or try setting GDAL_LIBRARY_PATH in your settings."
--
--
Ticket URL: <https://code.djangoproject.com/ticket/34375#comment:5>