.py scripts cause problems on the Windows command line. This was worked around to some degree by conda creating .py.exe entrypoints. However pip install refuses to do this and will only create .exe entrypoints (no .py).
So this change will mainly benefit Windows users. However all examples of package entry points I can find don't have the .py so this will make usage more 'standard'.
Calling the old .py scripts will now emit a warning.
Also taken the opportunity to call UseExceptions() to quieten the warnings with latest GDAL. And update the conda links. Plus add an extra note in INSTALL.txt about conda in case this is all people look at.
@neilflood we must do a release very shortly after merging this as the documentation will not match the existing release command line names (removed .py).
.py scripts cause problems on the Windows command line. This was worked around to some degree by conda creating
.py.exe
entrypoints. Howeverpip install
refuses to do this and will only create.exe
entrypoints (no .py).So this change will mainly benefit Windows users. However all examples of package entry points I can find don't have the .py so this will make usage more 'standard'.
Calling the old .py scripts will now emit a warning.
Also taken the opportunity to call
UseExceptions()
to quieten the warnings with latest GDAL. And update the conda links. Plus add an extra note in INSTALL.txt about conda in case this is all people look at.@neilflood we must do a release very shortly after merging this as the documentation will not match the existing release command line names (removed .py).