Use already activated venv

[khamaileon]

Question

I am in the process of switching from virtualenvwrapper + piptools to uv. The only thing stopping me from fully switching is the ability to activate a virtual environment and run some hooks (like cd ~/workspace/myproject). I've seen that's already a popular request so I decided to keep virtualenvwrapper for now.

However, when I run uv sync, I get this warning:

`VIRTUAL_ENV=/Users/me/.virtualenvs/myproject` does not match the project environment path `.venv` and will be ignored

The script then creates a .venv folder and completes the sync instead of using the already activated venv.

This behavior is odd because the documentation states the opposite: https://docs.astral.sh/uv/pip/environments/#discovery-of-python-environments

Am I missing something?

Platform

No response

Version

No response

[konstin]

uv sync uses .venv in your project independent of your system of activated environment for consistency in the project commands. If you need to specifically use a different environment, you can set UV_PROJECT_ENVIRONMENT to your venv location.

[khamaileon]

Thanks for your help. Here's the doc if someone else missed it: https://docs.astral.sh/uv/concepts/projects/config/#project-environment-path