I would have suggested to uninstall the offending proprietary software
:-), but perhaps checking that PYTHONPATH or PYTHONHOME are not defined
to an unexpected value will be sufficient
Le 12/01/2022 à 19:24, Rafael Lima a écrit :
## Expected behavior and actual behavior.
I installed gdal on a Windows environment using anaconda and tried
using one of the .py scripts (e.g., ogrmerge.py). I expected the
script to make use of the gdal installed in such an environment, but
it seems that the script finds another gdal installation (screenshot
below), thus throwing an error. My question seems to be related to the
one in
https://stackoverflow.com/questions/69328298/cannot-run-a-py-which-requires-a-gdal-module-in-anaconda-prompt-nor-in-command,
apparently unsolved. I was wondering what is the correct approach to
make sure gdal scripts find the correct gdal?
## Steps to reproduce the problem.
create a conda environment:
conda create -n test1 gdal
activate the environment
conda activate test1
call a gdal .py script
ogrmerge.py
In my case, that throws an error apparently because the script uses
another gdal installation:
## Operating system
Windows 10 Pro - 20H2 version
## GDAL version and provenance
GDAL==3.0.2
GDAL==3.4.0
Thank you!
Rafael
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
