e2309df85e
When a PEP 517 project file is present, pip will not install prerequisites in `site-packages`: https://pip.pypa.io/en/stable/reference/pip/#pep-517-and-518-support For the shell hook, this has the consequence that the generated temporary directory that is added to PYTHONPATH does not contain `site.py`. As a result, Python does not discover the Python module. Thus when a user executes nix-shell in a project, they cannot import the project's Python module. This change adds the `--no-build-isolation` option to pip when creating the editable environment, to correctly generate `site.py`, even when a `pyproject.toml` is present.
44 lines
1.1 KiB
Bash
44 lines
1.1 KiB
Bash
# Setup hook to use for pip projects
|
|
echo "Sourcing pip-build-hook"
|
|
|
|
pipBuildPhase() {
|
|
echo "Executing pipBuildPhase"
|
|
runHook preBuild
|
|
|
|
mkdir -p dist
|
|
echo "Creating a wheel..."
|
|
@pythonInterpreter@ -m pip wheel --no-index --no-deps --no-clean --no-build-isolation --wheel-dir dist .
|
|
echo "Finished creating a wheel..."
|
|
|
|
runHook postBuild
|
|
echo "Finished executing pipBuildPhase"
|
|
}
|
|
|
|
pipShellHook() {
|
|
echo "Executing pipShellHook"
|
|
runHook preShellHook
|
|
|
|
# Long-term setup.py should be dropped.
|
|
if [ -e pyproject.toml ]; then
|
|
tmp_path=$(mktemp -d)
|
|
export PATH="$tmp_path/bin:$PATH"
|
|
export PYTHONPATH="$tmp_path/@pythonSitePackages@:$PYTHONPATH"
|
|
mkdir -p "$tmp_path/@pythonSitePackages@"
|
|
@pythonInterpreter@ -m pip install -e . --prefix "$tmp_path" \
|
|
--no-build-isolation >&2
|
|
fi
|
|
|
|
runHook postShellHook
|
|
echo "Finished executing pipShellHook"
|
|
}
|
|
|
|
if [ -z "${dontUsePipBuild-}" ] && [ -z "${buildPhase-}" ]; then
|
|
echo "Using pipBuildPhase"
|
|
buildPhase=pipBuildPhase
|
|
fi
|
|
|
|
if [ -z "${shellHook-}" ]; then
|
|
echo "Using pipShellHook"
|
|
shellHook=pipShellHook
|
|
fi
|