-
Notifications
You must be signed in to change notification settings - Fork 659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Executables installed via uv
cannot be run from a subprocess on Windows
#1612
Comments
AlexWaygood
added
bug
Something isn't working
windows
Specific to the Windows platform
labels
Feb 17, 2024
I think that should be fixed by #1523 |
My local repro is now fixed -- thanks! However, I'm still seeing the strange errors over at AlexWaygood/typeshed-stats#189 (which is now using |
Since the original repro at the top of this issue is now fixed, I'll close this and open a new, more targeted issue |
This is the new issue: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Minimal repro in PowerShell:
The same commands work fine if I use the stdlib
venv
module to create the virtual environment and I usepip
to install black. Invokingblack
directly from the command line seems to work fine; it's only invoking it via a subprocess that doesn't seem to work.A consequence of this bug seems to be that it's impossible to run
coverage -m pytest
on Windows inside a GitHub Actions workflow if you've installedcoverage
usinguv
. Here's my attempt at switchingtypeshed-stats
to useuv
:uv
for installing requirements in CI AlexWaygood/typeshed-stats#189CI is now green everywhere, except on Windows, where invoking
coverage -m pytest
fails with the message:(Running
python -m coverage
works, but one test in my suite still fails, because I have a test that asserts that runningtypeshed-stats
as a standalone executable works, and I invoke the standalone executable using a subprocess for that test...)The text was updated successfully, but these errors were encountered: