uv use wrong interpreter when uv venv
, and activated wrong environment when activate venv
#2649
Labels
duplicate
This issue or pull request already exists
Run On
uv version: 0.1.24
OS: Windows 11
Problem Reproducing
I have multiple python version in my PC with aliases python, python310, and python311. I already install uv in python311 by
And then I check the other python
which is expected.
Then I trigger command for creating a virtual environment:
First Problem
The first problem is, uv use python alias (which is python 3.10.8) as interpreter.
Second Problem
After I activate the venv and pip freeze
It resulted the activated python interpreter of my other folder with installed packages, meanwhile my current Lib folder is empty.
Below is the full terminal interactions
The text was updated successfully, but these errors were encountered: