- `cargo run pip install ./scripts/editable-installs/black_editable`
- `cargo run pip install black --verbose`
e5b0cf7...
by
Charlie Marsh <email address hidden>
Add support for unnamed local directory requirements (#2571)
## Summary
For example: `cargo run pip install .`
The strategy taken here is to attempt to extract the package name from
the distribution without executing the PEP 517 build steps. We could
choose to do that in the future if this proves lacking, but it adds
complexity.
4d96255...
by
Charlie Marsh <email address hidden>
Enable unnamed requirements for direct URLs (#2569)
## Summary
This PR enables `uv pip install` to accept unnamed requirements, as long
as the requirement ends with the wheel or source distribution archive
name. For example: `cargo run pip install
~/Downloads/anyio-4.3.0.tar.gz`.
In subsequent PRs, I'll expand the scope of supported archives and
patterns.
ee211b3...
by
Charlie Marsh <email address hidden>
Add support for parsing unnamed URL requirements (#2567)
## Summary
First piece of https://github.com/astral-sh/uv/issues/313. In order to
support unnamed requirements, we need to be able to parse them in
`requirements-txt`, which in turn means that we need to introduce a new
type that's distinct from `pep508::Requirement`, given that these
_aren't_ PEP 508-compatible requirements.
Avoid repeating paths of workspace packages (#2573)
Scott schafer got me the idea: We can avoid repeating the path for
workspaces dependencies everywhere if we declare them in the virtual
package once and treat them as workspace dependencies from there on.
