Support for uv.sources

[bravhek]

What's the problem this feature will solve?

Resolve dependencies from non pypi sources like GitHub repos.

Describe the solution you'd like

Use uv's project dependency resolution. If a dependency has been declared in [tool.uv.project] resolve from that source instead of pypi (name colition)

[gaborbernat]

PR welcome... but I don't plan adding this myself.

[paveldikov]

I am interested in this feature and am happy to contribute but I think I could use some architectural debate/guidance.

To me it appears that root cause here is that uv.sources only kicks in when a package is being installed direct from pyproject.toml which is not what tox does. Rather it:

1. builds project (sdist -> wheel)
2. installs project dependencies
3. installs built wheel without dependencies

in separate stages, as opposed to doing a singular uv pip install {toxinidir} command.
Therefore uv's handling of sources simply does not kick in.

Coalescing into a single install stage/command would probably be very involved brain-surgery and probably break the tox model. Alternatively we could parse pyproject.toml and try to emulate uv's handling of sources, but that sounds architecturally icky.

Ideally I'd be able to force-feed a pyproject.toml as a configuration item to a uv command (without actually installing it - or having to convert to uv.toml schema) and then the source specification should natively kick in?

cc @charliermarsh in case there is a more elegant way of going about this

[gaborbernat]

Coalescing into a single install stage/command would probably be very involved brain-surgery and probably break the tox model. Alternatively we could parse pyproject.toml and try to emulate uv's handling of sources, but that sounds architecturally icky.

IMHO this is the path ahead.

[paveldikov]

Assuming you meant the former, this is interesting and I didn't expect that to be your preference!

It does make things easier, but means that there will be lots of no-op stages i.e..pkg and install_package_deps will have to be overridden into no-ops because install_package does it all in one fell swoop.

TBH this isn't unique to uv as pip install . does the same isolated-build-then-install dance in modern versions of pip. Maybe that could be a more general architectural simplification in tox although it is a much bigger bite than I can chew ATM!