From 361e9185c83166b44419e05e75fc8473875df6ea Mon Sep 17 00:00:00 2001
From: Mathieu Boespflug <m@tweag.io>
Date: Sat, 4 May 2019 19:09:31 +0200
Subject: [PATCH] linkchecker: fix bad interaction with python3

Previously, `nix-shell -p linkchecker python3` would lead to a broken
`python3` command. That's because Python 2 packages would pollute the
environment and confuse the interpreter. `linkchecker` has propagated
build inputs. So the solution is to use `pythonPath` instead, to avoid
the pollution.
---
 pkgs/tools/networking/linkchecker/default.nix | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pkgs/tools/networking/linkchecker/default.nix b/pkgs/tools/networking/linkchecker/default.nix
index 6e13d7fb94cb..acc6893d0cd5 100644
--- a/pkgs/tools/networking/linkchecker/default.nix
+++ b/pkgs/tools/networking/linkchecker/default.nix
@@ -19,7 +19,7 @@ python2Packages.buildPythonApplication rec {
   version = "9.3.1";
 
   nativeBuildInputs = [ gettext ];
-  propagatedBuildInputs = (with python2Packages; [ 
+  pythonPath = (with python2Packages; [
     requests
   ]) ++ [ gettext ];