Reported in IRC:
(19:23:05) shlevy: goibhniu: Well, $nose/lib/python2.7/site-packages/python-nose-1.2.1-nix-python-build-inputs.pth contains the path to python-coverage, presumably because coverage is a buildInput
(19:23:20) shlevy: goibhniu: But coverage is only needed at build time, this makes it a runtime dependency
do not create e.g pth file for build inputs
if they are really needed they will be in pth file created by
easy_install. If that does not work, they need to be put into
propagatedBuildInputs or the setup.py fixed.
I suspect @chaoflow or @shlevy have already fixed this. No python-nose-1.2.1-nix-python-build-inputs.pth gets created here when I install nose, only easy-install.pth
$ cat /nix/store/bnsk2a7i99x783nfdbwih5ykaifi7llb-python-nose-1.2.1/lib/python2.7/site-packages/python-nose-1.2.1-nix-python-build-inputs.pth
This is with latest nixpkgs (commit 129aa4d)
Yes indeed, sorry! I was looking in totally the wrong place. Checking it out now ...
In the current setup python package buildInputs could either be libraries used for compilation of c modules e.g. lxml or, as in this case python modules which are required for running the tests during build time.
To keep the python modules used for testing out of the installed module we could remove out the line:
createBuildInputsPth build-inputs "$buildInputStrings"
I have a feeling that we included this line because we thought modules required for running tests should be handled separately from buildInputs, but decided not to tackle this issue straight away. Does that sound right @chaoflow? It doesn't seem very useful to me personally to be able to run tests on installed modules. Perhaps the recent support for multiple outputs could help tidy this up.
At any rate, it doesn't bother me if this line stays or gos.
python2.6 compiles again, continuing improvements, like not creating a pth for buildInputs