-
Notifications
You must be signed in to change notification settings - Fork 790
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
Support absolute path on windows #1539
Comments
Yeah that seems wrong... |
Czaki
changed the title
Support absolute path on windos
Support absolute path on windows
Feb 16, 2024
Reproduced, will fix. |
This didn't go out in v0.1.3, but will be fixed soon. |
This is blocking currently |
👍 I’m hoping to fix it tomorrow. |
charliermarsh
added a commit
that referenced
this issue
Feb 20, 2024
## Summary The main change is that we need to have an explicit list of protocols we _do_ support (like `https`), so that when we see a Windows absolute path (`C:\...`), we don't treat the `C` as a protocol itself. Closes #1539.
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When plaing with tox integration I got two bug reports that suggest that uv is not properly interpreting absolute windows paths.
When try locally
On CI: https://github.com/napari/napari/actions/runs/7935590920/job/21669475977?pr=6668#step:12:51
It looks like there is a problem with parsing the Windows path. Did I'm correct?
The text was updated successfully, but these errors were encountered: