On Mon, Oct 25, 2010 at 1:47 PM, Sylvain Thénault < [email protected]> wrote:
> 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? I can understand that you want to keep your way of working, I am merely expressing my wishes as a user. I don't know the "develop" command that well, but I know it installs *.egg-link (.e.g, pylint.egg-link) files that point to each package's source tree. These link files are used to augment the module path like eggs, except that referred source trees are put on the path, so that you don't have to reinstall code after making changes. Arve
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
