Conversation
| requires = | ||
| tox>=4.51.0 | ||
| tox-uv | ||
| tox-uv-bare |
There was a problem hiding this comment.
Wait, what? Is it published under two names now? 🤔
There was a problem hiding this comment.
Bare doesn’t install uv as a dependency
| @@ -3,7 +3,7 @@ | |||
| [tox] | |||
| requires = | |||
There was a problem hiding this comment.
This looks like a use case for having tox to implement referencing this section from dep groups to dedupe the list..
cc @gaborbernat
There was a problem hiding this comment.
Im This Vase it’s more of. Belts and suspenders thing since we always run tox using uv. Maybe should be removed to fail loudly? Idk
There was a problem hiding this comment.
Well, my understanding is that this is for people that have tox as a primary pre-existing entry-point (and not uv) — tox then makes a managed venv under .tox/.tox/ and installs all the goodies + a newer version of itself. So to me this sounds like a more logical hook point for sticking automatic provisioning. I'm wondering, though, if tox's API allows plugins to extend this list — this would make for a powerful mechanism of setting up centralized ecosystem-centric infras.
I think this might also be in use by downstreams. But we'd have to ask @hroncok @befeleme @encukou @mgorny etc.
2 participants
Better reproducibility everywhere.