Closed abondrn closed 7 months ago
Should we consider re-implementing the poetry-export-plugin or calling it as a subprocess?
Similar to our policy on reading pip's configuration, I don't think we can do this. I think the bullets there are a good summary of why.
It might not be perfect, but it would be really helpful to have at least an attempt to import from pipenv configuration. You can get close with uv add -r <(pipenv requirements)
but then all package versions are pinned because pipenv requirements
is based on the lock file. The other piece would be reading from the Pipfile to specify the dependencies.
Related
When
uv pip install
is passedpoetry.lock
orPipfile.lock
(and any optional dependency groups, or extras) instead ofrequirements.txt
, it could attempt to install these in the uv environment. I can only speak for myself when I say this will speed up adoption of uv in some contexts we are using it, such as executing local tests or Docker pipelines.