nixpkgs/pkgs/development/interpreters/python/hooks/wheel-unpack-hook.sh

# Setup hook to use in case a wheel is fetched
echo "Sourcing wheel setup hook"

wheelUnpackPhase(){
    echo "Executing wheelUnpackPhase"
    runHook preUnpack

    mkdir -p dist
    cp "$src" "dist/$(stripHash "$src")"

#     runHook postUnpack # Calls find...?
    echo "Finished executing wheelUnpackPhase"
}

if [ -z "${dontUseWheelUnpack-}" ] && [ -z "${unpackPhase-}" ]; then
    echo "Using wheelUnpackPhase"
    unpackPhase=wheelUnpackPhase
fi
Split buildPythonPackage into setup hooks 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`). 2019-07-17 19:36:47 +01:00			`# Setup hook to use in case a wheel is fetched`
			`echo "Sourcing wheel setup hook"`

			`wheelUnpackPhase(){`
			`echo "Executing wheelUnpackPhase"`
			`runHook preUnpack`

			`mkdir -p dist`
			`cp "$src" "dist/$(stripHash "$src")"`

			`# runHook postUnpack # Calls find...?`
			`echo "Finished executing wheelUnpackPhase"`
			`}`

treewide: `Phase(s)?` variables are optional If these aren't defined, the stdenv defaults are used in the `Phase` case, or no extra phases are done, in the `*Phases` case. 2019-10-31 17:59:18 +00:00			`if [ -z "${dontUseWheelUnpack-}" ] && [ -z "${unpackPhase-}" ]; then`
Split buildPythonPackage into setup hooks 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`). 2019-07-17 19:36:47 +01:00			`echo "Using wheelUnpackPhase"`
			`unpackPhase=wheelUnpackPhase`
			`fi`