-
Notifications
You must be signed in to change notification settings - Fork 772
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
uvx (and uv) considerably slower in windows command prompt but fine in powershell #7025
Comments
Can you try using |
Thanks for the quick response! Running In CMD it takes a long time, haven't got it to complete yet, but in PS it finishes up quick. So maybe same issue still there?
|
So it ends up as a network timeout - but again, in PS and on MAC on same wifi there's no issue with timing out. Idk that
|
Very weird — sorry I have no idea why Windows behavior would be different across these two shells. |
Well so if i launch cmd.exe in powershell it works as expected ... idk what's going on there but doesn't seem like a uv problem that I can tell. Gonna close this. thank you for the time! |
FWIW I've now learned that running |
Running
uvx jupyter
in windows command prompt really chokes up for me, the progress bars start freezing up and progress becomes unclear. But in powershell everything runs with reasonable speed. This is using 0.4.4.I settled on this as a MRE, but I first came across this when using
uv run
with a script that launchesjupyter
. Was seeing terrible performance in command prompt, but fine in powershell, and fine on a mac on the same wifi.This snippet was my ultimate goal, to be run with
uv run
.Originally came to the GitHub issues through (#5073) but I think maybe it's not quite similar enough. Any thoughts or tips would be much appreciated!
The text was updated successfully, but these errors were encountered: