I agree...could be slightly inelegant to figure out what version of python
is used though...A system call to `where python` on windows would return
the interpreter on the path, and you could replace the '.exe' with '.dll'
(this is assuming python dll is always alongside the exe, but i think this
Sean,
> I suspect users will be find it very surprising if `which python` and the
> python interpreter used by VRT are not the same
Yes, we should probably make some effort to use the same python version as the
one that comes as default given the PATH. I've just opened
Hi Even, James:
I suspect users will be find it very surprising if `which python` and the
python interpreter used by VRT are not the same. Imagine starting python in
an environment created by virtualenv or conda that contains extension
modules like scikit-image, scikit-learn, You import
Hello, I'm experiencing some warnings in GDAL 2.1 and error messages (HTTP 401)
from the server.
In I'm getting some unwanted results.
However I am able to read features from the server, but I wonder why these
errors occur, and if I'm not getting all the information I should have gotten
if
excellent, working setting the PYTHONSO variable. Trying to match the
version of python on the path would be smart, but it is probably 'good
enough' to give PYTHONSO some prominence in the documentation - some kind
of warning on how python is discovered perhaps?
On 14 September 2016 at 20:20,
