Docs menu

Runtime versions

Which Python versions Primcloud supports, how to pin one via .python-version, and how to upgrade.

On this page

Primcloud installs the Python version your project asks for, resolved from a .python-version file at the root of your repo. If you don't ask for anything, you get the latest patch of Python 3.14.

Supported versions#

The Python versions you can install are part of the Primcloud Runtime. Each deployment's build log shows the exact version it installed.

Major Support status
3.10 Deprecated, in removal window
3.11 Deprecated, in removal window
3.12 Supported
3.13 Supported
3.14 Supported (default)
3.15 Supported

Each version installs its newest patch release. Only CPython is available, not PyPy, Jython, or other implementations.

Support follows Python's own support policy. A version past its end-of-life keeps building for a short while, then is removed; the build log gives the removal date for a version you've pinned.

Pinning a version#

Drop a .python-version file at the repo root with the major version you want:

.python-version
3.14

That installs the newest 3.14 release. We recommend this, so every rebuild picks up security fixes on its own.

You can pin an exact patch when you need to:

.python-version
3.13.14

We don't recommend it: an exact pin freezes your app on that patch until you bump the file by hand, so security fixes wait on you.

Format rules. One version per file. No quotes, no python- prefix, no wildcards. Comment lines are fine as long as they start with #.

uv requires .python-version. For uv projects the file is mandatory. Leave it out and the build fails with a "no Python version was specified" error. Run uv python pin 3.14 locally to create it, then commit the result.

runtime.txt no longer works. Primcloud reads the Python version from .python-version, not the older runtime.txt. If your repo still carries a runtime.txt, the build fails with a "runtime.txt file isn't supported" error. Delete it and add .python-version with the same major version.

Upgrading#

Bump the pin and redeploy:

  • Edit .python-version (3.13 → 3.14, say).
  • Commit and push.

The next build downloads the newer Python and reinstalls your dependencies against it, so the first build after a version change runs longer, then speed returns on the next deploy.

Read Python's What's New before jumping majors. Primcloud won't stop you from installing a version that then fails to import your code.

When a version drops out of support#

When a major reaches end-of-life on Python's schedule, Primcloud walks it through two stages:

  • Deprecation warning. Builds still succeed, and the build log shows a warning naming the removal date.
  • Removal. After the deprecation window, the version is gone. A build pinned to it fails with "the requested Python version has reached end-of-life."

To avoid a forced upgrade under time pressure:

  • Watch your build log for the deprecation warning and its removal date.
  • Bump .python-version to a supported major before that date.
  • Run your test suite against the new major locally before you deploy.

Python 3.10 is in that deprecation window now. Check your build log for the date it drops.