You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
awslocal on Windows doesn't seem to work properly with uv tool run --from awscli-local awslocal
The executable `awslocal` was not found.
warning: An executable named `awslocal` is not provided by package `awscli-local`.
The following executables are provided by `awscli-local`:
- awslocal
- awslocal.bat
Consider using `uv tool run --from awscli-local <EXECUTABLE_NAME>` instead.
The awslocal file is actually a script:
#!python.exe
"""
Thin wrapper around the "aws" commandlineinterface (CLI) forusewithLocalStack.
...
while for other tools it looks like a .exe is installed, which seems to work with uv.
This is probably caused by the fact that they provide the entry scripts as a path to file, not as module:function.
Using the provided .bat file does work, but it requires providing a different executable name based on the current OS and it looks like python detaches from the terminal when run from a batch script.
I'm not sure whether this is a problem with awslocal or uv. I thought I'd report it here first since this usage of setuptools seems legit.
The text was updated successfully, but these errors were encountered:
uv version:
uv 0.4.30 (61ed2a236 2024-11-04)
awslocal
on Windows doesn't seem to work properly withuv tool run --from awscli-local awslocal
The
awslocal
file is actually a script:while for other tools it looks like a
.exe
is installed, which seems to work withuv
.This is probably caused by the fact that they provide the entry scripts as a path to file, not as
module:function
.Using the provided
.bat
file does work, but it requires providing a different executable name based on the current OS and it looks like python detaches from the terminal when run from a batch script.I'm not sure whether this is a problem with awslocal or uv. I thought I'd report it here first since this usage of setuptools seems legit.
The text was updated successfully, but these errors were encountered: