from
Sylvain Thénault <sylvain.thenault at logilab dot fr>
to
Kring Gerhard <gerhard.kring at siemens dot com>
subject
Re: [Python-projects] WG: pyLint problems with inheritance
date
On Tuesday 04 January à 08:38, Kring Gerhard wrote:2005/01/04 10:51
> Hello Sylvain,
Hello
> thank you for your detailed response!
> I really want to propose broad usage of the pyLint Tools within our python projects.
> The only real blocking point is the "module location/import" problem...
yes, I personally think this problem is very annoying to, so I expect to
fix it in the next release.
> 1. Concerning the linelength problem:
> - my understanding is that you import the module and then do the code analysis based on this. With the imported module you no longer have the original source file lines, but the concatenated 'logical' lines.
no. The analysis is not based on a imported module but either on a ast
representation or on the raw file. Line lenght check is done on the raw
file, i.e. on 'physical' line
> This is currently not a problem for us, because before the pyLint run, we do our own checks based on the source file which include besides the linelength check also checks for invalid CR/LF sequences and invalid characters.
> Invalid CR/LF sequences lead to pyLint aborts...
could you send me a test file which is correctly importable but which
make pylint aborting ?
> 2. Concerning comment lines in config files:
> How do you process these config files?
> Do you use the Python ConfigParser?
yes (actually a higher level module built on top of both ConfigParser
and optparse).
regards
PS: I'm ccing python-projects mailing list since pylint discussion
should take place there.
--
Sylvain Thénault LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects