Add --compile-bytecode to uv python install and uv python upgrade to compile the standard library
#17088
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CodSpeed Performance ReportMerging #17088 will not alter performanceComparing Summary
|
5644a1b to
d08b115
Compare
d08b115 to
cc0d3f9
Compare
konstin
reviewed
Dec 11, 2025
Member
konstin
left a comment
There was a problem hiding this comment.
Looks good! Added some smaller comments.
zanieb
reviewed
Dec 11, 2025
cc0d3f9 to
6c39c61
Compare
6c39c61 to
7cc9212
Compare
ee3a32b to
03d0b75
Compare
konstin
approved these changes
Dec 18, 2025
zanieb
reviewed
Dec 18, 2025
zanieb
reviewed
Dec 18, 2025
Comment on lines
1193
to
1195
| warn_user_once!( | ||
| "Standard library bytecode compilation is not supported for pyodide" | ||
| ); |
Member
There was a problem hiding this comment.
This could be pretty annoying if UV_COMPILE_BYTECODE is just set globally? I think we usually want warnings to be actionable, and this one isn't really. I might just move this into verbose logs?
Member
There was a problem hiding this comment.
We could differentiate between explicit --compile-bytecode and implicit UV_COMPILE_BYTECODE as we just did for UV_GIT_LFS, I guess. Then the action is "remove the flag", but it's weird if you do
uv python install cpython-3.12 pyodide-3.12 --compile-bytecode
Contributor
Author
There was a problem hiding this comment.
I had spoken about the warnings stuff with konsti yesterday, see the new commit, maybe that's better?
zanieb
reviewed
Dec 18, 2025
| ); | ||
| if explicit_request { | ||
| warn_user!( | ||
| "Skipping standard library bytecode compilation for {} as it misreported its location.", |
Member
There was a problem hiding this comment.
What does it mean for it to have "misreported its location"? I don't think this will make sense to a user. What action can they take to resolve this?
Member
There was a problem hiding this comment.
Talk to us and/or the maintainer of that Python distribution to get that sysconfig fixed, otherwise it's just silently broken.
Looks like windows python builds have a different number of files.
Currently this reliably hits a timeout on Windows. At some point we should revisit this.
19ce460 to
9755976
Compare
6e1e99b to
cdf398c
Compare
konstin
approved these changes
Jan 12, 2026
zaniebot
pushed a commit
to zaniebot/uv
that referenced
this pull request
Jan 14, 2026
Identifies that PR astral-sh#17088 (--compile-bytecode feature) introduced cache initialization for `uv python install`, which breaks Docker builds when HOME is unset or set to "/". The cache directory falls back to /.cache/uv which requires root permissions. In v0.9.24, uv python install did not initialize the cache at all.
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Jan 17, 2026
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | patch | `0.9.24` → `0.9.26` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (astral-sh/uv)</summary> ### [`v0.9.26`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0926) [Compare Source](astral-sh/uv@0.9.25...0.9.26) Released on 2026-01-15. ##### Python - Add CPython 3.15.0a5 ##### Enhancements - Add a hint to update uv when a managed Python download is not found ([#​17461](astral-sh/uv#17461)) - Improve cache initialization failure error message ([#​17469](astral-sh/uv#17469)) - Improve error message for abi3 wheels on free-threaded Python ([#​17442](astral-sh/uv#17442)) - Add support for `--no-sources-package` ([#​14910](astral-sh/uv#14910)) ##### Preview features - Add `METADATA.json` and `WHEEL.json` in uv build backend ([#​15510](astral-sh/uv#15510)) - Add support for GCS request signing ([#​17474](astral-sh/uv#17474)) - Adjust the process ulimit to the maximum allowed on startup ([#​17464](astral-sh/uv#17464)) ##### Bug fixes - Lock to avoid concurrent refresh of pyx tokens ([#​17479](astral-sh/uv#17479)) ##### Documentation - Add linting and formatting instructions to the CONTRIBUTING guide ([#​17470](astral-sh/uv#17470)) - Avoid rendering `pyproject.toml` examples for more system-level settings ([#​17462](astral-sh/uv#17462)) ### [`v0.9.25`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0925) [Compare Source](astral-sh/uv@0.9.24...0.9.25) Released on 2026-01-13. ##### Python - Add CPython 3.15.0a4 - Upgrade Tcl/Tk used by CPython to 9.0 ##### Enhancements - Add `--compile-bytecode` to `uv python install` and `uv python upgrade` to compile the standard library ([#​17088](astral-sh/uv#17088)) - Allow disabling `exclude-newer` per package ([#​16854](astral-sh/uv#16854)) - Broadcast `WM_SETTINGCHANGE` on `uv tool update-shell` ([#​17404](astral-sh/uv#17404)) ##### Preview features - Detect workspace from `uv run` target ([#​17423](astral-sh/uv#17423)) ##### Bug fixes - Avoid unwrapping size for file responses ([#​17434](astral-sh/uv#17434)) - Use keyring authentication when retrieving `tool@latest` version ([#​17448](astral-sh/uv#17448)) - Use latest Pyodide version for each python version ([#​17372](astral-sh/uv#17372)) - Improve trampoline file handle closing ([#​17374](astral-sh/uv#17374)) - Fix error message when installing musl python on armv7 ([#​17213](astral-sh/uv#17213)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi44MC4xIiwidXBkYXRlZEluVmVyIjoiNDIuODEuOCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90IiwiYXV0b21hdGlvbjpib3QtYXV0aG9yZWQiLCJkZXBlbmRlbmN5LXR5cGU6OnBhdGNoIl19-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Implement #16408.
Currently doesn't avoid recompiling the bytecode when it is already compiled, which I initially thought could be fine but then realised that it would be annoying if you have the environment variable set.
Covers upgrades, installs, reinstalls, and compiling existing installs. But not certain about the UX.
pyodide is weird and currently gets skipped by the heuristic I came up with.
Test Plan
Styling of the status report was manually tested, there is a new test for testing the actual functionality.