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

[Edward K. Ream]

On Mon, Jul 7, 2008 at 3:53 AM, Sylvain Thénault <
sylvain.thenault at logilab.fr> wrote:

>
> > 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.


Actually, running pylint.bat from the directory above the leo directory
appears to work, which is an even better solution than changing the path.

Thanks for your help.

Edward
--------------------------------------------------------------------
Edward K. Ream email: edreamleo at gmail.com
Leo: http://webpages.charter.net/edreamleo/front.html
--------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.logilab.org/pipermail/python-projects/attachments/20080707/38e8f3ee/attachment.htm