Use console_scripts instead of scripts #88
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
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.
uvseems to not be able to run scripts installed viascripts=insetup.pyon Windows; it doesn't seem to accept the provided.batscript (see astral-sh/uv#8888)This change bypasses the issue by installing awslocal as a console_script, which produces an exe when installed on Windows.
You can verify that
python3 -m venv venv; venv\Scripts\activate.bat; pip install .producesvenv\Scripts\awslocal.exewhen ran on Windows with my changes.This also fixes the issue with
uv:uv tool install .installsawslocal.exein the binaries directory.This still does not fix the issue in #84, so the program still segfaults, but at least it's installed properly.