ab3eeabfed
Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs" sounds like an imperative rather than a noun phrase.
111 lines
3.5 KiB
Nix
111 lines
3.5 KiB
Nix
/* This function provides a generic Python package builder. It is
|
|
intended to work with packages that use `setuptools'
|
|
(http://pypi.python.org/pypi/setuptools/), which represents a large
|
|
number of Python packages nowadays. */
|
|
|
|
{ python, setuptools, wrapPython, lib, offlineDistutils, setuptoolsSite }:
|
|
|
|
{ name, namePrefix ? "python-"
|
|
|
|
, buildInputs ? []
|
|
|
|
, propagatedBuildInputs ? []
|
|
|
|
, # List of packages that should be added to the PYTHONPATH
|
|
# environment variable in programs built by this function. Packages
|
|
# in the standard `propagatedBuildInputs' variable are also added.
|
|
# The difference is that `pythonPath' is not propagated to the user
|
|
# environment. This is preferrable for programs because it doesn't
|
|
# pollute the user environment.
|
|
pythonPath ? []
|
|
|
|
, installCommand ?
|
|
''
|
|
easy_install --always-unzip --prefix="$out" .
|
|
''
|
|
|
|
, preConfigure ? "true"
|
|
|
|
, buildPhase ? "true"
|
|
|
|
, doCheck ? true
|
|
|
|
, checkPhase ?
|
|
''
|
|
runHook preCheck
|
|
python setup.py test
|
|
runHook postCheck
|
|
''
|
|
|
|
, postInstall ? ""
|
|
|
|
, ... } @ attrs:
|
|
|
|
# Keep extra attributes from ATTR, e.g., `patchPhase', etc.
|
|
python.stdenv.mkDerivation (attrs // {
|
|
inherit doCheck buildPhase checkPhase;
|
|
|
|
name = namePrefix + name;
|
|
|
|
phases = "unpackPhase patchPhase configurePhase buildPhase installPhase checkPhase fixupPhase distPhase";
|
|
|
|
buildInputs = [ python wrapPython setuptools ] ++ buildInputs ++ pythonPath;
|
|
|
|
# setuptoolsSite is responsible for loading pth files
|
|
propagatedBuildInputs = propagatedBuildInputs ++ [ setuptoolsSite ];
|
|
|
|
buildInputStrings = map toString buildInputs;
|
|
|
|
pythonPath = [ setuptools] ++ pythonPath;
|
|
|
|
preConfigure = ''
|
|
PYTHONPATH="${offlineDistutils}/lib/${python.libPrefix}/site-packages:$PYTHONPATH"
|
|
${preConfigure}
|
|
'';
|
|
|
|
installPhase = ''
|
|
mkdir -p "$out/lib/${python.libPrefix}/site-packages"
|
|
|
|
echo "installing \`${name}' with \`easy_install'..."
|
|
export PYTHONPATH="$out/lib/${python.libPrefix}/site-packages:$PYTHONPATH"
|
|
${installCommand}
|
|
|
|
# A pth file might have been generated to load the package from
|
|
# within its own site-packages, rename this package not to
|
|
# collide with others.
|
|
eapth="$out/lib/${python.libPrefix}"/site-packages/easy-install.pth
|
|
if [ -e "$eapth" ]; then
|
|
# move colliding easy_install.pth to specifically named one
|
|
mv "$eapth" $(dirname "$eapth")/${name}.pth
|
|
fi
|
|
|
|
# Remove any site.py files generated by easy_install as these
|
|
# cause collisions. If pth files are to be processed a
|
|
# corresponding site.py needs to be included in the PYTHONPATH.
|
|
#
|
|
# leave them until we have a better solution: see #209
|
|
#rm -f "$out/lib/${python.libPrefix}"/site-packages/site.py*
|
|
|
|
${postInstall}
|
|
'';
|
|
|
|
postFixup =
|
|
''
|
|
wrapPythonPrograms
|
|
|
|
# If a user installs a Python package, she probably also wants its
|
|
# dependencies in the user environment (since Python modules don't
|
|
# have something like an RPATH, so the only way to find the
|
|
# dependencies is to have them in the PYTHONPATH variable).
|
|
if test -e $out/nix-support/propagated-build-inputs; then
|
|
ln -s $out/nix-support/propagated-build-inputs $out/nix-support/propagated-user-env-packages
|
|
fi
|
|
|
|
createBuildInputsPth build-inputs "$buildInputStrings"
|
|
for inputsfile in propagated-build-inputs propagated-native-build-inputs; do
|
|
if test -e $out/nix-support/$inputsfile; then
|
|
createBuildInputsPth $inputsfile "$(cat $out/nix-support/$inputsfile)"
|
|
fi
|
|
done
|
|
'';
|
|
})
|