On Mon, Feb 14, 2011 at 2:07 PM, Arve Knudsen <[email protected]>wrote:
> Salut > > On Mon, Feb 14, 2011 at 1:03 PM, Pierre-Yves David < > [email protected]> wrote: > >> On Mon, Feb 14, 2011 at 10:52:03AM +0100, Arve Knudsen wrote: >> > Hi >> > >> > Using pylint 0.23.0 (astng 0.21.1, common 0.54.0) I see the problem that >> > pylint picks up the egg installation of my project instead of the >> sources, >> > even though the latter is placed first on PYTHONPATH. Also, this problem >> > seems to be recently been introduced, as I have been pylint-ing my >> project >> > for some time without seeing this problem. In fact, trying now with my >> old >> > pylint installation (0.21.0, astng 0.20.1, common 0.50.2), I do not see >> this >> > behaviour. >> > >> > Is this a known problem? If not, how do we go about solving it? >> >> This is the expected behaviour of .egg (one would call it a bug but it's a >> *feature*). Setuptools overwrite the pythonpath to put path of directories >> of >> all installed .egg in front. Do not use setuptools and egg. >> > > I use distribute rather than setuptools, for what it's worth. Isn't that > the current distutils replacement? > > I am also aware of eggs being preferred to non-egg packages on PYTHONPATH > when using pkg_resources . However, the latter is solved by generating a > .egg-info in your source tree (which is on PYTHONPATH). Due to there being a > .egg-info in my source tree, pkg_resources detects my source tree as an egg. > It is only pylint that apparently gets it wrong. > Are you still of the opinion that this is a non-issue? Considering that distutils2 is apparently not production-ready, I can't see how to get around this issue apart from reverting to distutils1 (no thanks). Arve
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
