Previously it was missing a runtime dependency on setuptools:
[kier@saelli:~/checkouts/nixpkgs]$ $(nix-build -A python27Packages.pylint --no-out-link)/bin/pylint
Traceback (most recent call last):
File "/nix/store/0k8h6n6nxjcs2j5jp54mfppjbx37hrrg-python2.7-pylint-1.9.5/bin/.pylint-wrapped", line 6, in <module>
from pylint import run_pylint
File "/nix/store/0k8h6n6nxjcs2j5jp54mfppjbx37hrrg-python2.7-pylint-1.9.5/lib/python2.7/site-packages/pylint/__init__.py", line 11, in <module>
from .__pkginfo__ import version as __version__
File "/nix/store/0k8h6n6nxjcs2j5jp54mfppjbx37hrrg-python2.7-pylint-1.9.5/lib/python2.7/site-packages/pylint/__pkginfo__.py", line 25, in <module>
from pkg_resources import parse_version
ImportError: No module named pkg_resources
With this change, the same command now correctly prints pylint's help text.
This only applies to Python 2.
pyenchant is broken on macOS and also no longer actively developed.
pylint has made this an optional dependency that is no longer part of the
default test suite.
See this issue for more discussion:
https://github.com/PyCQA/pylint/issues/1900
The `buildPython*` function computes name from `pname` and `version`.
This change removes `name` attribute from all expressions in
`pkgs/development/python-modules`.
While at it, some other minor changes were made as well, such as
replacing `fetchurl` calls with `fetchPypi`.
pylint (using Python 2.7) got propagated into python3Packages.spyder
so Python 2.7 setup-hook was used instead of python34.
Now that pylint is part of pythonPackages attribute set, pylint is
used with python3.4 as a base.
It doesn't make sense to build tools/applications with three different
python interpreter versions, so move them out of python modules list.
Also reverts 53ffc6e0ef.
