use entrypoints instead of .py scripts for the command line #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We must also amend the conda build when it picks up the new version to also provide the non- |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.py scripts cause problems on the Windows command line. This was worked around to some degree by conda creating
.py.exeentrypoints. Howeverpip installrefuses to do this and will only create.exeentrypoints (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).