Use entry_points to fix script installation on windows #712
Conversation
This file contains hidden or 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
the-nic
force-pushed
the
fix-entrypoint-windows
branch
2 times, most recently
from
1e61396 to
53ce472
Compare
the-nic
changed the title
the-nic
force-pushed
the
fix-entrypoint-windows
branch
from
53ce472 to
f8e572f
Compare
Contributor
Author
|
removed commits from #711 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The setuptools
scriptentry does not work under windows. Instead, use theentrypointsand adjust the scripts so they can be used in windows, too (this will generate.exefiles in the Scripts directory when working in windows.