Repository navigation
Warn when .python-version conflicts with uv venv -p <version> in projects #8847
Description
Activity
Do you have a
.python-versionfile in the directory that pins to 3.13, maybe?Doh! I do have a
.python-versionfile in that directory pinned to 3.13. I'm not sure where it came from.I removed it and now it works as expected.
@charliermarsh You are the best. Your response time is truly insane. Thank you sir!
Reacted by Charlie MarshReally glad I could help! (I wonder if we should've warned in the first
uv venvinvocation? \cc @zanieb)I view this as 100% my own fault.
But if you could warn users to let them know about this potentially unanticipated behavior, that would be fantastic.
Thanks for the ping, yeah it seems like we should probably warn there if you're changing to virtual environment to something we won't use in future project invocations.
uv runshould also say where it sourced that version from. I might have made that easier in #6370.- changed the title
[-][Bug?] uv venv --python 3.12 creates a Python 3.13.0 virtual environment[/-][+]Warn when `.python-version` conflicts with `uv venv -p <version>` in projects[/+]on Nov 5, 2024 Any update on this? We encountered a situation where it delete a
.venvthat took some time to install...
Summary
I ask
uvto install a Python 3.12 virtual environment and then ask it to run a command using what I assume is the default virtual environment and it actually runs it using Python 3.13.Perhaps I am misunderstanding how
uvis supposed to work but this is a very non-intuitive customer experience.How to reproduce
$ uv venv --python 3.12 Using CPython 3.12.6 Creating virtual environment at: .venv Activate with: source .venv/bin/activate $ uv run python -V Using CPython 3.13.0 Removed virtual environment at: .venv Creating virtual environment at: .venv ...Platform details