Actually, it wasn't entirely true that pylint 0.21.0 doesn't pick up the egg installation, there are just a lot fewer occurrences (which I must've missed at first glance). There is actually a mix of modules (part of the same package) being found in the source tree and in the installed egg.
Arve On Mon, Feb 14, 2011 at 10:52 AM, Arve Knudsen <[email protected]>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? > > Arve >
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
