dependencies that are *not* propagated to the user environment
(as opposed to `propagatedBuildInputs'). For instance, if you
install `iotop', you typically don't want its Python dependencies
polluting the user environment.
* buildPythonPackage: some cleanup (e.g. use function argument
defaults instead of `if attrs ? foo then attrs.foo else []').
svn path=/nixpkgs/branches/modular-python/; revision=26571
The generic 'buildPythonPackage' function used to use the build/install command
"easy_install" unconditionally. That didn't work for python-numpy, for
instance, because the package wants "setup.py" run with additional parameters
to determine the fortran compiler of choice. The newly introduced function
argument 'installCommand' allows to implement this. By passing that parameter,
the default build command can be overridden.
svn path=/nixpkgs/trunk/; revision=22786
a worthy goal to move the Python packages that are currently in
all-packages.nix into a single attribute set, but this doesn't
require moving python-packages.nix or the other changes made to that
file. The Python packages in all-packages.nix should simply be
moved to python-packages.nix, and ideally changed to use
buildPythonPackage.
svn path=/nixpkgs/trunk/; revision=21196
- cleanup python libraries:
* moving all python libraries into a attr set into a directory
so that expressions can be used for both: python 2.5 and 2.6 easily
* disabling packages which don't build
svn path=/nixpkgs/trunk/; revision=21142