This is one of the big reasons I’m in favour of making these behave just like an in-tree venv and incorporating the --mainpath PATH option into the proposal. That way, even if the auto-activation only works implicitly from the project’s base directory, there’d be two ways to resolve the issue:
- explicitly activate the virtual environment, taking implicit activation out of the question entirely
- pass
--mainpath ../../(adjust as needed) in order to tell the interpreter where to look for the venvs to auto-activate