You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mirror CPython and support 𝜋thon in 3.14 venvs #16240
In CPython 3.14's venv module there is a new alias for the python interpretter alongside python3 or python3.14 called 𝜋thon. This is an easter egg for this minor version of CPython, and it would be neat if uv also added this alias.
In the spirit of the original easter egg, would probably be best to leave it out of the release notes and just quietly add it.
One downside to uv supporting this, is that uv would have to keep support for this for many more years than the upstream CPython project does, due to uv supporting historic versions of Python. (ie: uv will likely need to support Python 3.14 for many years after 3.14 reaches upstream EOL)
In contrast, the upstream CPython project was already able to remove support from main (where Python 3.15 is now being developed), so won't be carrying the feature in any newer branch: python/cpython#134037
Reacted by Daniel Hollas, Y.D.X. and Agriya Khetarpal
Could someone explain to me, a layman when it comes to Python packaging and tooling, what extra support burden this imposes on the dev team? It seems like the PR's code is all that is needed, and shouldn't need much more support than that. Some things I can envision:
It may be troublesome to remember to replicate the code if some future feature should support this.
It may cause new issues popping up with "𝜋thon not working anymore", which increases triaging times.
I wouldn't even advertise the feature or claim it's a "supported feature". I understand the desire to ship polished software that always runs, which uv is (it's a joy to use; I love it!), and this increases the bug surface in a sense. But it also seems like a bit of harmless fun.
However, I may be missing something, so I welcome the opportunity to learn about this 🤓.
I'm also having trouble when trying to install torch via uv, but I'd get this error:
uv pip install --index-url https://rocm.nightlies.amd.com/v2/gfx1151/ --pre torch torchaudio torchvision
× No solution found when resolving dependencies:
╰─▶ Because all versions of torch have no wheels with a matching Python ABI
tag (e.g., `cp314`) and you require torch, we can conclude that your
requirements are unsatisfiable.
hint: You require CPython 3.14 (`cp314`), but we only found wheels for
`torch` (v2.10.0a0+rocm7.10.0a20251024) with the following Python ABI
tags: `cp311`, `cp312`, `cp313`
At first, I thought it was an uv problem, but now that I see pytorch/pytorch#156856, it seems like a chain of external dependencies and package managers that makes Python more fun to use.
@hoonsubin that's unrelated, uv supports 3.14 — this issue is about supporting an easter egg added in 3.14. That issue you linked is the correct issue to follow for pytorch 3.14 support.
Activity
danielhollas commentedon Oct 10, 2025
There was a PR for this already but received (a light) pushback.
#13341
Personally I'm enjoying that Python still retains it's Monty Pyzhon quirkiness so would be nice if uv did this, but it's up to the maintainers. :-)
edmorley commentedon Oct 11, 2025
One downside to uv supporting this, is that uv would have to keep support for this for many more years than the upstream CPython project does, due to uv supporting historic versions of Python. (ie: uv will likely need to support Python 3.14 for many years after 3.14 reaches upstream EOL)
In contrast, the upstream CPython project was already able to remove support from
main(where Python 3.15 is now being developed), so won't be carrying the feature in any newer branch:python/cpython#134037
rafalkrupinski commentedon Oct 12, 2025
It could be just an easter egg, not documented or supported...
sebastian-correa commentedon Oct 15, 2025
Could someone explain to me, a layman when it comes to Python packaging and tooling, what extra support burden this imposes on the dev team? It seems like the PR's code is all that is needed, and shouldn't need much more support than that. Some things I can envision:
𝜋thonnot working anymore", which increases triaging times.I wouldn't even advertise the feature or claim it's a "supported feature". I understand the desire to ship polished software that always runs, which
uvis (it's a joy to use; I love it!), and this increases the bug surface in a sense. But it also seems like a bit of harmless fun.However, I may be missing something, so I welcome the opportunity to learn about this 🤓.
hoonsubin commentedon Oct 25, 2025
Just adding on to this thread.
I'm also having trouble when trying to install torch via
uv, but I'd get this error:At first, I thought it was an
uvproblem, but now that I see pytorch/pytorch#156856, it seems like a chain of external dependencies and package managers that makes Python more fun to use.zanieb commentedon Oct 25, 2025
@hoonsubin that's unrelated, uv supports 3.14 — this issue is about supporting an easter egg added in 3.14. That issue you linked is the correct issue to follow for pytorch 3.14 support.