.python Version ^new^ -

Tells pyenv to skip its own shims and use the system Python (e.g., /usr/bin/python ). Dangerous for production but sometimes used for system scripts.

Even without native support, these tools respect the Python version that is active in the shell – which pyenv sets from .python-version .

To help tailor this setup for your specific workstation, let me know: .python version

uv venv --python 3.13

Your shell might cache the path to python . After changing .python-version , run hash -r (bash) or rehash (zsh/pyenv). Tells pyenv to skip its own shims and

Always include your .python-version file in your Git repository. It functions as vital infrastructure documentation alongside your requirements.txt , pyproject.toml , or Pipfile . This makes onboarding new team members as easy as running a fresh git clone . Do Not: Confuse it with Virtual Environments

: Run pyenv local 3.11.0 to set the version and create the file. 3. Usage & Compatibility To help tailor this setup for your specific

Have a specific version migration issue? Check the official Porting to Python 3.13 guide.

Before locking a project to a specific interpreter, ensure it is available locally. pyenv install 3.12.2 Use code with caution. Step 2: Set the Local Version

There is no "official" cross‑platform tool from Python for installing and switching between multiple Python versions. However, the community has built several excellent solutions.

The file can be committed to Git, acting as a lightweight piece of documentation for project requirements.