79650448

Date: 2025-06-02 23:31:03
Score: 0.5
Natty:
Report link

I think there might be.

The approach would be to use one tool to manage the shared env -- say, pyenv -- and another to manage the project-specific one -- say uv.

You'd set the shared dependencies by having an active pyenv virtualenv and use pip to install the common dependencies. Then uv with its own venv would be used, via uv pip install, to layer in project-specific dependencies.

Currently I've used pyenv + uv together, but I point uv's "venv" to the pyenv environment and so am not doing this layering. so... I'm thinking this could work but haven't tested it. This questions was asked a while ago but if there's still interest I could see if the idea presented in this answer actually works.

Reasons:
  • Long answer (-0.5):
  • No code block (0.5):
  • Low reputation (0.5):
Posted by: sofend