-
Notifications
You must be signed in to change notification settings - Fork 615
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
Missing test coverage for tool.uv
behaviours
#3943
Comments
We should also test the |
See also: #4298 |
konstin
changed the title
Add missing tests for
Missing for Jul 9, 2024
tool.uv
behaviourtool.uv
behaviours
konstin
added a commit
that referenced
this issue
Jul 16, 2024
Add support for path dependencies from a package in one workspace to a package in another workspace, which it self has workspace dependencies. Say we have a main workspace with packages `a` and `b`, and a second workspace with `c` and `d`. We have `a -> b`, `b -> c`, `c -> d`. This would previously lead to a mangled path for `d`, which is now fixed. Like distribution paths, we split workspace paths into an absolute install path and a relative (or absolute, if the user provided an absolute path) lock path. Part of #3943
charliermarsh
changed the title
Missing
Missing test coverage for Jul 30, 2024
tool.uv
behaviourstool.uv
behaviours
This was referenced Aug 12, 2024
charliermarsh
added a commit
that referenced
this issue
Aug 12, 2024
Did these! They surfaced a few bugs too which is great. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #3904, we added support for a whole class of new
tool.uv
behaviors, but no tests for them yet.tool.uv
information from index packages, url archives or path archives, neithertool.uv.sources
nortool.uv.workspace
.tool.uv.sources
inheritance from the workspace to the project works.tool.uv.sources
entry don't match #4603The text was updated successfully, but these errors were encountered: