uvx gimme-aws-creds fails on Windows

[knowsuchagency]

uvx seems to correctly identify the gimme-aws-creds executable but cannot invoke it.

This is with version 0.3.4, specifically on Windows

PS C:\Users\FOO> uvx gimme-aws-creds
Installed 45 packages in 2.42s
The executable `gimme-aws-creds` was not found.
warning: An executable named `gimme-aws-creds` is not provided by package `gimme-aws-creds`.
The following executables are provided by `gimme-aws-creds`:
- gimme-aws-creds
- gimme-aws-creds-autocomplete.sh
- gimme-aws-creds.cmd

[zanieb]

Interesting, thanks for the report! Seems like a classic weird Windows thing.

[samypr100]

Hmmm, they don't define console_scripts entrypoints, just a script section which points to other scripts.

[samypr100]

From https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#scripts

Although setup() supports a scripts keyword for pointing to pre-made scripts to install, the recommended approach to achieve cross-platform compatibility is to use Creating executable scripts entry points

Seems like using scripts doesn't work well from a cross-platform perspective, especially on Windows.

[zanieb]

Ah interesting. Thanks for the context. Does this work with pipx?

[knowsuchagency]

It works on Mac, but not Windows. That's actually true for both pipx and uvx