Creating a venv with uv does not use the correct python version #3630

FlorianGD · 2024-12-02T14:26:59Z

FlorianGD
Dec 2, 2024

Hello,

First, thanks for the great tool, I have been using it and advising people to use it for quite some time, it is really valuable ! I regularly update the tool via cargo install-update, and it seems I have been bitten by using the latest version.

Describe the bug
When setting a new python project, I want mise to create and activate the virtual env for me, using the version given in .mise.toml. It used to work fine.
The latest version seems to use uv to create the virtual env, resulting in the wrong python version being installed.

To Reproduce
With the setting python.venv_stdlib as false, and with the following .mise.toml

[env]
_.file = ".env"
_.python.venv = { path = ".venv", create = true }

[tools]
python = { version = "3.10" }

When I enter the directory with no .venv created, this is what I see:

mise creating venv with uv at: ~/REDACTED/.venv
Using CPython 3.11.10
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate.fish

Notice the using CPython 3.11.10 when I want python 3.10 as per the .mise.toml file.

Moreover, I do not have the pip binary in the virtualenv. Manually activating the env does not change it.

$ python -V
Python 3.11.10
$ which pip
/HOME/.local/share/mise/installs/python/3.10.13/bin/pip
$ source .venv/bin/activate.fish
$ which pip
/HOME/.local/share/mise/installs/python/3.10.13/bin/pip

If I change the setting python.venv_stdlib as true, then I have the correct behavior (though, the creation is slower because it does not use uv anymore)

$ mise settings set python.venv_stdlib true
$ rm -rf .venv
mise creating venv with stdlib at: REDACTED/.venv
$ which python
REDACTED/.venv/bin/python
$ python -V
Python 3.10.13
$ which pip
REDACTED/.venv/bin/pip

Expected behavior
I'd like to create the virtualenv with uv and having the correct python version installed in the virtual environment.

I have uv installed externally of the project, using pipx and python version 3.12 if that matters.
Setting python.uv_venv_auto does not seem to change as this project does not use uv.lock.

mise doctor output

version: 2024.11.37 linux-x64 (7ac5ab3 2024-11-30)
activated: yes
shims_on_path: no

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Sat, 30 Nov 2024 01:03:00 +0000
  Rust Version: rustc 1.82.0 (f6e511eec 2024-10-15)
  Profile: release

shell:
  /usr/bin/fish
  fish, version 3.7.1

dirs:
  cache: ~/.cache/mise
  config: ~/.config/mise
  data: ~/.local/share/mise
  shims: ~/.local/share/mise/shims
  state: ~/.local/state/mise

config_files:
  ~/.config/mise/config.toml
  ~/REDACTED/.mise.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
  chezmoi  https://github.com/joke/asdf-chezmoi.git#53f30be
  go       https://github.com/kennyp/asdf-golang.git#d4f1d65
  haskell  https://github.com/asdf-community/asdf-haskell.git#499d84c
  java     https://github.com/rtx-plugins/rtx-java.git#6c6790c
  jq       https://github.com/azmcode/asdf-jq.git#a13dea7
  meson    https://github.com/asdf-community/asdf-meson.git#212ecdb
  ninja    https://github.com/asdf-community/asdf-ninja.git#e196e02
  yarn     https://github.com/twuni/asdf-yarn.git#376c540

toolset:
  core:[email protected]

env_vars:
  MISE_SHELL=fish

settings:
  experimental         true  ~/.config/mise/config.toml
  python.uv_venv_auto  true  ~/.config/mise/config.toml
  python.venv_stdlib   false ~/.config/mise/config.toml

2 warnings found:

1. plugin go overrides a core plugin

2. plugin java overrides a core plugin

No problems found

Additional context
I use ubuntu 20.04.

jdx · 2024-12-02T16:46:47Z

jdx
Dec 2, 2024
Maintainer

does MISE_PYTHON_UV_VENV_AUTO work?

0 replies

FlorianGD · 2024-12-03T09:07:00Z

FlorianGD
Dec 3, 2024
Author

Hi, not I tried to set it via the settings and it does not change anything (it is set to true in the mise doctor output above). I changed it false but it did not change the behavior.

0 replies

syhol · 2024-12-14T18:42:09Z

syhol
Dec 14, 2024

Wrong python version in venv auto creation

When I enter the directory with no .venv created, this is what I see:
mise creating venv with uv at: ~/REDACTED/.venv
Using CPython 3.11.10
Creating virtual environment at: .venv
Activate with: source .venv/bin/activate.fish

I can't recreate this.

I tried in a fresh mise environment Debian 12 bookworm, click here to see what I did.

~/Code/sandbox
❯ docker run --pull=always -it --rm --entrypoint bash jdxcode/mise:latest
[docker] $ docker run --pull=always -it --rm --entrypoint bash jdxcode/mise:latest
latest: Pulling from jdxcode/mise
Digest: sha256:47b5d9a3dfcdc81563c6de6c759301ace63753d28547752610377a6560e4230f
Status: Image is up to date for jdxcode/mise:latest
root@a7f380f997a9:/mise# cd /srv

Install and open fish shell then activate mise

root@a7f380f997a9 /srv# apt update; apt install fish -y; exec fish -l;
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Reading package lists... Done
...
Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
root@a7f380f997a9 /srv# mise activate fish | source
root@a7f380f997a9 /srv# ps
  PID TTY          TIME CMD
    1 pts/0    00:00:00 fish
  386 pts/0    00:00:00 ps

I removed the pre-install python tool in the docker container:

root@a7f380f997a9 /srv# echo "" > /mise/config.toml
root@a7f380f997a9 /srv# mise uninstall --all
mise [email protected] ✓ uninstalled

I created a symlink so python point to system python at 3.11.2:

root@a7f380f997a9 /srv# ln -s /usr/bin/python3 /usr/bin/python
root@a7f380f997a9 /srv# which python
/usr/bin/python
root@069e412150ca /srv# python --version
Python 3.11.2

I install uv and copied your settings from mise doctor into the global config

root@a7f380f997a9 /srv# mise use -g uv
mise [email protected] ✓ installed
mise /mise/config.toml tools: [email protected]
root@a7f380f997a9 /srv# mise settings experimental=true
root@a7f380f997a9 /srv# mise settings python.uv_venv_auto=true
root@a7f380f997a9 /srv# mise settings python.venv_stdlib=false
root@a7f380f997a9 /srv# mise settings
Key                  Value Source
experimental         true  /mise/config.toml
python.uv_venv_auto  true  /mise/config.toml
python.venv_stdlib   false /mise/config.toml

Create your .mise.toml:

root@a7f380f997a9 /srv# echo '[env]
                        _.file = ".env"
                        _.python.venv = { path = ".venv", create = true }

                        [tools]
                        python = { version = "3.10" }
                        ' >issue-3325/.mise.toml
root@a7f380f997a9 /srv# mise trust ./issue-3325
mise trusted /srv/issue-3325

Now cd in and see the venv wasn't created:

root@a7f380f997a9 /srv# cd issue-3325/
mise WARN  no venv found at: /srv/issue-3325/.venv

To create a virtualenv manually, run:
python -m venv /srv/issue-3325/.venv
root@a7f380f997a9 /s/issue-3325# ls -a
./  ../  .mise.toml

Now run mise install and see the python version is correct in the new .venv:

root@a7f380f997a9 /s/issue-3325# mise install
mise WARN  libgit2 failed: cannot force update branch 'master' as it is the current HEAD of the repository.; class=Reference (4)
mise hint use multiple versions simultaneously with mise use [email protected] [email protected]
mise hint installing precompiled python from indygreg/python-build-standalone
if you experience issues with this python (e.g.: running poetry), switch to python-build by running mise settings python.compile=1
mise WARN  no venv found at: /srv/issue-3325/.venv

To create a virtualenv manually, run:
python -m venv /srv/issue-3325/.venv
mise [email protected] ✓ installed                                                                                                                                                                       mise creating venv with uv at: /srv/issue-3325/.venv
Using CPython 3.10.16 interpreter at: /mise/installs/python/3.10.16/bin/python
Creating virtual environment at: .venv
root@a7f380f997a9 /s/issue-3325# .venv/bin/python --version
Python 3.10.16

Leave the dir, rm the venv, and re-enter to see the correct version is used.

root@a7f380f997a9 /s/issue-3325# cd ../
root@a7f380f997a9 /srv# rm -rf issue-3325/.venv/
root@a7f380f997a9 /srv# cd issue-3325/
mise creating venv with uv at: /srv/issue-3325/.venv
Using CPython 3.10.16 interpreter at: /mise/installs/python/3.10.16/bin/python
Creating virtual environment at: .venv

Unless you can help me recreate the issue, I can't do much to help. Perhaps you can share your path? Maybe you have something overriding your python version. If we can recreate this issue then it's definitely a bug we should try to fix.

No pip in .venv

I don't get pip in venv even when I manually create it with with uv venv, so I think this is expected behaviour.

I tested this in the same environment I created to test the first issue, click here to see what I did.

root@a7f380f997a9 /s/issue-3325# sed 's/true/false/' -i .mise.toml
root@a7f380f997a9 /s/issue-3325# cat .mise.toml
[env]
_.file = ".env"
_.python.venv = { path = ".venv", create = false }

[tools]
python = { version = "3.10" }

root@a7f380f997a9 /s/issue-3325# rm -rf .venv
mise WARN  no venv found at: /srv/issue-3325/.venv

To create a virtualenv manually, run:
python -m venv /srv/issue-3325/.venv
root@a7f380f997a9 /s/issue-3325# uv venv
Using CPython 3.10.16 interpreter at: /mise/installs/python/3.10.16/bin/python
Creating virtual environment at: .venv
root@a7f380f997a9 /s/issue-3325# ls .venv/bin
activate  activate.bat  activate.csh  activate.fish  activate.nu  activate.ps1  activate_this.py  deactivate.bat  pydoc.bat  python@  python3@  python3.10@

Next steps

Wait for author @FlorianGD to provide reproducible steps or tell us if he can't recreate it in a fresh environment.

0 replies

syhol · 2024-12-14T20:39:53Z

syhol
Dec 14, 2024

I've been digging into this bit of the code today and yes, it uses whatever is in your path.

I have a hunch you are running into the issue described here: https://github.com/jdx/mise/issues/2718 tldr; the theory is that you've manually activated a venv (e.g. venv/bin/activate), and mise currently doesn't override that.

Can you start a fresh shell, make sure you have no active venvs, then try to recreate the issue again?

3 replies

FlorianGD Dec 18, 2024
Author

Hi, thanks for your investigation. I managed to reproduce the issue. You need to install python 3.11 with both uv and install python 3.10 with mise before going into the directory. Then when you cd into to directory, the venv is created with uv's python:

# The above steps before cd'ing into issue-3325
root@cce9a730db03 /srv # mise install [email protected]
mise hint installing precompiled python from indygreg/python-build-standalone
if you experience issues with this python (e.g.: running poetry), switch to python-build by running mise settings python.compile=1
mise [email protected] ✓ installed 
root@cce9a730db03 /srv# uv python install 3.11
Installed Python 3.11.11 in 5.18s
 + cpython-3.11.11-linux-x86_64-gnu
root@cce9a730db03 /srv# mkdir issue-3325
root@cce9a730db03 /srv# echo '[env]
                        _.file = ".env"
                        _.python.venv = { path = ".venv", create = true }
                        [tools]
                        python = { version = "3.10" }' >issue-3325/.mise.toml
root@cce9a730db03 /srv# mise trust issue-3325/
mise trusted /srv/issue-3325
root@cce9a730db03 /srv# cd issue-3325/
mise creating venv with uv at: /srv/issue-3325/.venv
Using CPython 3.11.11
Creating virtual environment at: .venv
root@cce9a730db03 /s/issue-3325# which python
/srv/issue-3325/.venv/bin/python
root@cce9a730db03 /s/issue-3325# python -V
Python 3.11.11
root@cce9a730db03 /s/issue-3325# ls -l .venv/bin/python
lrwxrwxrwx 1 root root 76 Dec 18 12:59 .venv/bin/python -> /root/.local/share/uv/python/cpython-3.11.11-linux-x86_64-gnu/bin/python3.11*
root@cce9a730db03 /s/issue-3325# echo $PATH | tr ' ' '\n'
/srv/issue-3325/.venv/bin
/mise/installs/uv/0.5.10/uv-x86_64-unknown-linux-musl
/mise/installs/python/3.10.16/bin
/usr/local/cargo/bin
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin
/sbin
/bin

syhol Dec 19, 2024

Great thanks, I think I've found the problem. I'm working on a fix now.

syhol Dec 19, 2024

Should be resolved in the next release: #3698

Uh oh!

Creating a venv with uv does not use the correct python version #3630

Uh oh!

FlorianGD Dec 2, 2024

Replies: 4 comments · 3 replies

Uh oh!

Uh oh!

jdx Dec 2, 2024 Maintainer

Uh oh!

FlorianGD Dec 3, 2024 Author

Uh oh!

Uh oh!

syhol Dec 14, 2024

Wrong python version in venv auto creation

No pip in .venv

Next steps

Uh oh!

syhol Dec 14, 2024

Uh oh!

Uh oh!

FlorianGD Dec 18, 2024 Author

Uh oh!

syhol Dec 19, 2024

Uh oh!

syhol Dec 19, 2024

FlorianGD
Dec 2, 2024

Replies: 4 comments 3 replies

jdx
Dec 2, 2024
Maintainer

FlorianGD
Dec 3, 2024
Author

syhol
Dec 14, 2024

syhol
Dec 14, 2024

FlorianGD Dec 18, 2024
Author