3 ms·
This library can use any version of Python 3.11, which you can install alongside your existing 3.10.9 without changing your global python version. I don't typic
by mrlatinos 1y ago
This library can use any version of Python 3.11, which you can install alongside your existing 3.10.9 without changing your global python version. I don't typically work in Windows so the codeblock below is AI generated, but follows the path I would normally take - manage installed python versions using pyenv, changing the python version only for this directory via .python_version, and then creating uv environment using that.
```
:: Step 1: Install pyenv-win (make sure Git is installed)
git clone https://github.com/pyenv-win/pyenv-win.git https://github.com/pyenv-win/pyenv-win.git "$env:USERPROFILE\.pyenv"
:: Step 2: Add pyenv to PATH (run or add to your profile)
$env:PYENV = "$env:USERPROFILE\.pyenv\pyenv-win"
$env:PATH += ";$env:PYENV\bin;$env:PYENV\shims"
:: Step 3: Restart your terminal or reload environment if needed
:: (you can paste the above $env:... lines again after restart)
:: Step 4: Install Python 3.11
pyenv install 3.11.9
:: Step 5: Set the local Python version for your project folder
cd C:\devel\us-routing-master\us_routing
pyenv local 3.11.9
:: Step 6: Verify correct Python is selected
pyenv which python # should point to 3.11.x
:: Step 7: Create uv environment using Python 3.11
uv venv .venv --python "$(pyenv which python)"
:: Step 8: Activate the environment
.venv\Scripts\activate
:: Step 9: Install your package
uv pip install us-routing
```
pyenv is a great way to have many versions of Python installed, whether or not your global is mapped to the latest. You don't even need to set the local .python_version.. you could just do `uv venv .venv --python=python3.11`