py-defs.mk: Define PYTHON_RUNNER
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 4m15s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m35s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 4m18s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 4m54s
CI / Packaging test (push) Successful in 0s
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 4m15s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m35s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 4m18s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 4m54s
CI / Packaging test (push) Successful in 0s
PYTHON_RUNNER is defined in py-run.mk but is more generally useful, e.g. for hand-rolled test Makefiles. It's also a cheap definition. Lift it into py-defs.mk instead. Signed-off-by: Jan Lindemann <jan@janware.com> Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v1.1.0
This commit is contained in:
parent
66d1a117a4
commit
85ddd44cd1
1 changed files with 2 additions and 1 deletions
|
|
@ -19,6 +19,8 @@ else
|
|||
PY_SITE_PACKAGES_PATH := $(shell $(PYTHON) -c "import site; print([d for d in site.getsitepackages() if d.find('/local/') == -1][0])")
|
||||
endif
|
||||
|
||||
PYTHON_RUNNER ?= $(PYTHON)
|
||||
|
||||
PY_SRC_PY ?= $(wildcard *.py)
|
||||
PY_LOCAL_PY = $(PY_SRC_PY)
|
||||
PY_INSTALL_PY = $(filter-out __init__.py,$(PY_SRC_PY))
|
||||
|
|
|
|||
Loading…
Reference in a new issue