f7e28bf5d8
This commit splits the `buildPythonPackage` into multiple setup hooks. Generally, Python packages are built from source to wheels using `setuptools`. The wheels are then installed with `pip`. Tests were often called with `python setup.py test` but this is less common nowadays. Most projects now use a different entry point for running tests, typically `pytest` or `nosetests`. Since the wheel format was introduced more tools were built to generate these, e.g. `flit`. Since PEP 517 is provisionally accepted, defining a build-system independent format (`pyproject.toml`), `pip` can now use that format to execute the correct build-system. In the past I've added support for PEP 517 (`pyproject`) to the Python builder, resulting in a now rather large builder. Furthermore, it was not possible to reuse components elsewhere. Therefore, the builder is now split into multiple setup hooks. The `setuptoolsCheckHook` is included now by default but in time it should be removed from `buildPythonPackage` to make it easier to use another hook (curently one has to pass in `dontUseSetuptoolsCheck`).
17 lines
634 B
Bash
17 lines
634 B
Bash
# Setup hook for checking whether Python imports succeed
|
|
echo "Sourcing python-imports-check-hook.sh"
|
|
|
|
pythonImportsCheckPhase () {
|
|
echo "Executing pythonImportsCheckPhase"
|
|
|
|
if [ -n "$pythonImportsCheck" ]; then
|
|
echo "Check whether the following modules can be imported: $pythonImportsCheck"
|
|
cd $out && eval "@pythonCheckInterpreter@ -c 'import os; import importlib; list(map(lambda mod: importlib.import_module(mod), os.environ[\"pythonImportsCheck\"].split()))'"
|
|
fi
|
|
}
|
|
|
|
if [ -z "$dontUsePythonImportsCheck" ]; then
|
|
echo "Using pythonImportsCheckPhase"
|
|
preDistPhases+=" pythonImportsCheckPhase"
|
|
fi
|