py-defs.mk: Honor PY_INSTALL_INIT_PY = false
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 8m8s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m12s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 7m43s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m58s
CI / Packaging test (push) Successful in 0s
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 8m8s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m12s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 7m43s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m58s
CI / Packaging test (push) Successful in 0s
PY_ALL_PY is derived from PY_SRC_PY, which wildcards *.py in the module directory, so a checked-in __init__.py enters the install list unconditionally. PY_INSTALL_INIT_PY only gates the later append of __init__.py, which covers files generated at build time. Setting it to false thus had no effect on an existing __init__.py, which was still installed together with its .pyc. Filter __init__.py out of PY_ALL_PY. When PY_INSTALL_INIT_PY is true, the existing append adds it back, so generated and checked-in __init__.py files are installed as before. When it is false, an existing __init__.py is now excluded from PY_ALL_PY and therefore also from PY_INSTALLED_PY and PY_PYC. Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v0.84.2 Signed-off-by: Jan Lindemann <jan@janware.com>
This commit is contained in:
parent
419b3f59f4
commit
bd78657588
1 changed files with 1 additions and 1 deletions
|
|
@ -20,7 +20,7 @@ else
|
|||
endif
|
||||
|
||||
PY_SRC_PY ?= $(wildcard *.py)
|
||||
PY_ALL_PY = $(PY_SRC_PY)
|
||||
PY_ALL_PY = $(filter-out __init__.py,$(PY_SRC_PY))
|
||||
|
||||
ifneq ($(PYTHON_MAJOR),3)
|
||||
PY_PYC = $(patsubst %.py,%.pyc,$(PY_ALL_PY))
|
||||
|
|
|
|||
Loading…
Reference in a new issue