| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Use faster archive compression in pull-request builds (#1371) Pull-request builds spend time compressing archives with the release settings. Use a `fast` profile with Zstandard level 3, long-distance matching, and `window_log=27` in pull-request workflows. The default `small` profile keeps level 22 for local and release builds. For the 488.8 MB uncompressed `cpython-3.14.9-x86_64-unknown-linux-gnu-pgo+lto` tar archive, median compression wall time fell from 273.13 s to 2.94 s (92.8× faster), while the compressed archive grew from 114.6 MB to 148.8 MB (+29.8%). These are two runs per profile on one pinned AMD EPYC-Genoa CPU on Linux, with a warm filesystem cache and `zstandard==0.25.0` (`libzstd` 1.5.7). The speedup applies to archive compression only. --------- Co-authored-by: zaniebot <242828183+zaniebot@users.noreply.github.com> | 14 天前 | |
rewrite R2 publishing in Python (#1051) This rips out the mirror uploading logic from the `pythonbuild` rust CLI and moves it to Python, mainly because the rust aws sdk is clearly not mature enough to support our use case, as evidenced by https://github.com/astral-sh/python-build-standalone/issues/1047 I've also had to start using `--no-dev` on some existing `uv run` invocations because `moto` wouldn't cleanly install in some build jobs (like when building CPython for Windows). ## Test plan Apart from unit tests, there's now an integration test with a local, mocked S3 provider (using `moto`). Dry run release on this branch: https://github.com/astral-sh/python-build-standalone/actions/runs/23550742376 | 7 个月前 | |
rewrite R2 publishing in Python (#1051) This rips out the mirror uploading logic from the `pythonbuild` rust CLI and moves it to Python, mainly because the rust aws sdk is clearly not mature enough to support our use case, as evidenced by https://github.com/astral-sh/python-build-standalone/issues/1047 I've also had to start using `--no-dev` on some existing `uv run` invocations because `moto` wouldn't cleanly install in some build jobs (like when building CPython for Windows). ## Test plan Apart from unit tests, there's now an integration test with a local, mocked S3 provider (using `moto`). Dry run release on this branch: https://github.com/astral-sh/python-build-standalone/actions/runs/23550742376 | 7 个月前 | |
Use patch files for Windows source changes (#1388) Windows builds encode fixed CPython and OpenSSL changes as inline replacements, and the xz fallback can leave a partially modified project when a later replacement fails. Move these edits into version-selected patches applied with `git apply`, normalizing line endings for CRLF project files and failing the build when a patch no longer applies. Build-specific paths and versions remain generated in Python. Remove the obsolete `_sqlite3.vcxproj` and `_freeze_importlib` rewrites for the supported CPython versions. Co-authored-by: zaniebot <242828183+zaniebot@users.noreply.github.com> | 12 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 14 天前 | ||
| 7 个月前 | ||
| 7 个月前 | ||
| 12 天前 |