from
Andreas Amoroso <a.amoroso at freenet dot de>
to
Sylvain Thenault <syt at logilab dot fr>
subject
Re: PyLint (fwd)
date
2004/05/10 18:38
Sylvain Thénault schrieb am 10.05.2004 14:37:
>Please, please, don't send me HTML mails. Anyway, see comments below
>
>
I am sorry, should be text this time :-[
>On Monday 10 May à 12:12, Andreas Amoroso wrote:
>
>
>>One thing I'm not sure about : did you want to have one file per checked
>>module or one file per module/package specified on the command line ?
>>(currently it's the latter, plus one file for statistic reports if any)
>>
>> </pre>
>></blockquote>
>>Basically both options would be OK as long as file output is available
>>at all.<br>
>>
>>
>
>Ok, so I'll let this as is for the moment.
>
>
>
>> <blockquote type="cite">
>> <pre wrap="">Additionally, please consider to include an empty __init__.py
>>in the logilab directory of the common installer as the absence of this
>>file prevents PyLint from starting.
>> </pre>
>> </blockquote>
>> <pre wrap=""><!---->
>>hum, the setup.py script of both pylint and common should create the
>>file if it doesn't exists. Do you have installed them using the regular
>>"python setup.py install" command ?
>>
>> </pre>
>></blockquote>
>>To be honest, I do not remember. I think I used a binary installer, but
>>I might have created it myself. Anyway, there seems to be something
>>missing as I know that somebody else encountered the same problem (and
>>was not interested enough to solve it himself, apparently).<br>
>>
>>
>
>I've just tried it and it worked for me.
>
>
>
>>BTW, I am currently using PyLint to analyze a little program that uses
>>"relative imports" (imports from files in the same dir as the main
>>module). I have two questions related to this:<br>
>>1. Why are these relative imports considered to be bad (flagged with
>>warnings)<br>
>>
>>
>
>because there are some conditions where Python messes with relative
>imports. For instance, see (long url...) :
>
>http://groups.google.com/groups?hl=fr&lr=&ie=UTF-8&oe=UTF-8&frame=right&th=2f19e83f13f481da&seekm=87adq8jsq1.fsf%40tux.ntw23.fr#link3
>
>
>
Thanx for the hint, I was not aware of the problem.
>>2. Is there (and if not should there be) an option to disable specific
>>warnings?<br>
>>
>>
>
>yep. See the --include-ids, --disable-msg and --enable-msg options.
>
>
Thanx again.
>
>
>>These are not too urgent, of course, but if the answer to the second
>>question should be no I think the proposed option would be worth
>>considering for future releases. And while I am at it, I would consider
>>it a plus if one could be more specific about naming conventions for
>>identifiers (e.g. separate rules for global functions and member
>>functions and the like). This all leads to the customization issues you
>>probably have been discussing all the way, but still I could not resist
>>;-)<br>
>>
>>
>
>ok, I've added a specific regexp for method names instead of using the
>same for functions / methods. Do you see something else ?
>
>
>
Nope, but I will keep your email address in case that changes :-)
>>However, not to leave the wrong impression, I like PyLint even in its
>>present state and consider it very useful.<br>
>>
>>
>
>I did not get a wrong impression... I'm always happy to get some
>feedback from pylint users, and even more when there is a patch or some
>features wishes. Anyway, it's always nice to receive something like "I
>like PyLint" ;)
>
>regards
>
>
Best regards