[Python-projects] Workaround for this serious pylint bug?

[Sylvain Thénault]

On Wed, Jul 02, 2008 at 01:46:51PM -0500, Edward K. Ream wrote:
> On Wed, Jul 2, 2008 at 12:47 PM, Maarten ter Huurne <
> maarten.ter.huurne at philips.com> wrote:
> 
> > python-projects-bounces at lists.logilab.org wrote on 2008-07-02 07:25:10 PM:
> >
> > > Suppose pylint-leo.bat contains:
> > >
> > > echo A demonstration of the pylint bug
> > > call pylint.bat test\pylintTest\subClass.py
> > --rcfile=test\pylint-leo-rc.txt
> >
> > Try running pylint from the "pylintTest" directory. On my system, the E1101
> > only occurs when pylint is run with a higher up directory as current working
> > directory. This is probably related to the warning about "Relative import
> > 'baseClass'".
> >
> 
> This works for the simple example given, but alas it doesn't seem to work
> for the actual Leo files.
> 
> The problem may be that Leo has imports of the form:
> 
> import leo.core.x as x
> 
> These imports require that the Leo be run from the directory above the leo
> directory.  This might affect pylint somehow.  Anyway, there is still no
> joy.

pylint is avoiding sys.path manipulation, so the directory containing
the leo package should be in your python path.

-- 
Sylvain Thénault                               LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian:  http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
Python et calcul scientifique:           http://www.logilab.fr/science