packages/lang/python/python-installer/patches, branch master

python-installer: allow flit_core 4.x as the build backend

2026-08-10T17:17:38Z

installer caps flit_core<4 in its build-system, so its /host build fails with "Missing dependencies: flit_core<4" against flit-core 4.0.2. flit_core 4 builds it unchanged; relax the upper bound. Signed-off-by: Alexandru Ardelean

python-installer: update to 1.0.0

2026-04-16T04:08:59Z

Update package to 1.0.0. This is the first stable release. Changes since 0.7.0: - Dropped support for Python 3.7, 3.8, 3.9; added Python 3.13/3.14 - Added --overwrite-existing and --validate-record CLI options - Support installing multiple wheels in a single invocation - Security: fixed a path traversal bug - Do not install __pycache__ directories from wheels - Switch to stream-based validation instead of in-memory (lower memory) - Sort entries before writing RECORD; fixed Windows relative path bug - Complete type annotations with strict mypy enforcement - API change: SchemeDictionaryDestination.overwrite_existing now defaults to True (was False); update patch 001 accordingly Remove patch 001-don-t-raise-error-if-file-exists.patch and set '--overwrite-existing' in build scripts. Signed-off-by: Alexandru Ardelean

python-installer: patch behavior for when script file exists

2025-11-08T09:21:38Z

This seems to happen when re-triggering a build. The destination path is already there, so this exception gets raised. Another approach is to do 'make package//clean' and re-trigger the build. But that becomes annoying. Signed-off-by: Alexandru Ardelean