On Wed, Jul 2, 2008 at 12:47 PM, Maarten ter Huurne <<a href="mailto:maarten.ter.huurne@philips.com">maarten.ter.huurne@philips.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<p><tt><a href="mailto:python-projects-bounces@lists.logilab.org" target="_blank">python-projects-bounces@lists.logilab.org</a> wrote on 2008-07-02 07:25:10 PM:<br>
<br>
</tt></p><div class="Ih2E3d"><tt>> Suppose pylint-leo.bat contains: </tt><br>
<tt>></tt><br>
<tt>> echo A demonstration of the pylint bug <br>
> call pylint.bat test\pylintTest\subClass.py --rcfile=test\pylint-leo-rc.txt</tt><br>
<br>
</div><tt>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'".</tt></div>
</blockquote><div><br>This works for the simple example given, but alas it doesn't seem to work for the actual Leo files.<br><br>The problem may be that Leo has imports of the form:<br><br>import leo.core.x as x<br><br>
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.<br><br>Edward <br></div></div>