On Mon, Oct 25, 2010 at 11:46:17AM +0200, Arve Knudsen wrote: > Hi > > As I tried to install pylint from Mercurial through pip, I discovered that > pylint is in effect not installable in development mode (i.e. "setup.py > develop"). The reason is that pylint only creates the "pylint" package when > it is installed in the normal manner, while development installation points > to the raw source directory (with no "pylint" package). Can you please make > development installation work?
The easiest way to use pylint in "developpment mode" is to adjust your PYTHONPATH environment variable to include the parent directory of your pylint checkout. B ecarefull with any previously egginstalled pylint as egg break PYTHONPATH mechanisms. Regards -- Pierre-Yves logilab.fr
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
