Others have answered most of your questions, I won't repeat the answers
here, but only join the choir to stress that pylint needs tuning to
your coding style. An obvious case is camelCaseMethodNames versus
underscored_method_names, but there are also a lot of issues. The
default pylint settings
Hello:
I ran the new pylint and my code and I had a few questions on why those
are warnings or what I can do to fix them:
1) W: 0: Too many lines in module (1587)
Why is 1587 considered too many lines? Would there be necessarily be an
advantage to split it up into 2 or 3 files? Can I
Michael Yanowitz escribió:
Hello:
I ran the new pylint and my code and I had a few questions on why those
are warnings or what I can do to fix them:
2) C: 0: Missing required attribute __revision__
What is this? Is that for CVS? I don't use CVS (we use SVN). I have not
seen
* Michael Yanowitz wrote:
I ran the new pylint and my code and I had a few questions on why those
are warnings or what I can do to fix them:
1) W: 0: Too many lines in module (1587)
Why is 1587 considered too many lines? Would there be necessarily be
an
advantage to split
In [EMAIL PROTECTED], Michael
Yanowitz wrote:
2) C: 0: Missing required attribute __revision__
What is this? Is that for CVS? I don't use CVS (we use SVN). I have not
seen any sample code which includes this tag yet. But if I include
__revision 1.0 somewhere in the code it will
Em Sex, 2006-04-21 às 13:49 -0400, Michael Yanowitz escreveu:
I ran the new pylint and my code and I had a few questions on why those
are warnings or what I can do to fix them:
You can ignore the warnings you don't like with the --disable-msg
option. Also, you can add a header to the file to
