On 25 octobre 12:33, Arve Knudsen wrote: > On Mon, Oct 25, 2010 at 11:54 AM, Nicolas Chauvat < > [email protected]> wrote: > > > Hi, > > > > On Mon, Oct 25, 2010 at 11:46:17AM +0200, Arve Knudsen wrote: > > > 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? > > > > Please send a patch or hg bundle and we will be happy to apply it. > > > I guess my solution would be to move the source code to a "pylint" > directory, is this acceptable?
no, since that would break the way we organize things at Logilab. What does setup.py develop do actually? -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
