Why is .venv created on every uv command invocation despite the environment being available?

[aaqibb13]

If I am creating a virtual environment using uv via the following:

uv venv venv

and then activating the virtual environment it via:

source venv/bin/activate

Shouldn't the already created virtual environment (venv in this case) be referenced on the subsequent uv command invokations?
Why is the .venv still created?

As per the docs:
If the venv directory is not PEP 405 compliant, that's when the already present virtual environment will be ignored.
But if my venv is already PEP 405 complaint since I created it via uv itself, why is this happening?
Am I missing something here?

[zanieb]

Yeah, we don't respect activated environments in projects. See #6834 and linked discussions

https://docs.astral.sh/uv/pip/environments/#using-a-virtual-environment is part of the uv pip documentation and specific to that subsection of uv.

See https://docs.astral.sh/uv/concepts/projects/layout/#the-project-environment for documentation on environments in projects.