python2Packages: keep separate (bootstrapped-)pip

Currently there is only one line difference regarding bootstrapped-pip,
but this will change in the future with the whole Python world moving
towards PEP 517.
This commit is contained in:
Frederik Rietdijk
2021-03-23 10:43:45 +01:00
parent 252ae44416
commit 983c453eec
3 changed files with 119 additions and 2 deletions
+8 -2
View File
@@ -22,7 +22,10 @@ let
namePrefix = python.libPrefix + "-";
bootstrapped-pip = callPackage ../development/python-modules/bootstrapped-pip { };
bootstrapped-pip = if isPy3k then
callPackage ../development/python-modules/bootstrapped-pip { }
else
callPackage ../development/python-modules/bootstrapped-pip/2.nix { };
# Derivations built with `buildPythonPackage` can already be overriden with `override`, `overrideAttrs`, and `overrideDerivation`.
# This function introduces `overridePythonAttrs` and it overrides the call to `buildPythonPackage`.
@@ -5122,7 +5125,10 @@ in {
pint = callPackage ../development/python-modules/pint { };
pip = callPackage ../development/python-modules/pip { };
pip = if isPy3k then
callPackage ../development/python-modules/pip { }
else
callPackage ../development/python-modules/pip/20.nix { };
pipdate = callPackage ../development/python-modules/pipdate { };