Re: [Python-projects] pylint #4581 proposed fix

2010-03-17 Thread Donovan Lee Wanhoy
Hi, Is there a reason to make it optional, rather than have it enabled at all > times? I assumed that the bug ticket said to make it optional. Attached is the same code except there is no option check. Hope this one is okay. Donovan Lee Wanhoy On Wed, Mar 17, 2010 at 4:44 AM, Sylvain Thénault <

Re: [Python-projects] Output improvements

2010-03-17 Thread Emile Anclin
On Wednesday 17 March 2010 18:37:23 Maarten ter Huurne wrote: > On Wednesday 17 March 2010, Sarah Strong wrote: > > And before I sign off, I'd like to throw my support behind the idea > > of disabling convention warnings by default. Can we ticket this and > > address it as part of our output fixes

Re: [Python-projects] Output improvements

2010-03-17 Thread Maarten ter Huurne
On Wednesday 17 March 2010, Sarah Strong wrote: > New ticket: Truncate repeated warnings > two options: > > Enabled by default, use --unabridged to show all warnings > message: > [ More warnings in this category, use --unabridged to show them all ] > > or > > Disabled by default, use --truncate

Re: [Python-projects] Output improvements

2010-03-17 Thread Sarah Strong
Hey, thanks for the great feedback on our output improvements. I'd just like to confirm what we'll be working on before I ticket the new behaviour New ticket: Truncate repeated warnings two options: Enabled by default, use --unabridged to show all warnings message: [ More warnings in this categor

Re: [Python-projects] pylint #18860: warn on assert( a, b ?) patch

2010-03-17 Thread Emile Anclin
On Monday 15 March 2010 12:50:13 Colin Morris wrote: > If it were possible to check a little more carefully what's being > asserted, then we could give a very specific message. As I understand > it, we're warning against the case where someone is trying to assert > some boolean expression along wit

Re: [Python-projects] Proposed output improvements

2010-03-17 Thread Maarten ter Huurne
On Wednesday 17 March 2010, Mads Kiilerich wrote: > It seems like pylint have different goals with different focus and > emphasis. > > The man page says: > pylint - python code static checker > > I think this is what I want. I would like pylint to be more like a > "unix" command line too

Re: [Python-projects] pylint #4581 proposed fix

2010-03-17 Thread Sylvain Thénault
On 17 mars 09:28, Maarten ter Huurne wrote: > > All I did was: > > - add an option, no-docstring-overridden that when invoked > > --no-docstring-overridden=y, it won't check the docstring for a method > > that is overridden. > > Is there a reason to make it optional, rather than have it enabled at

Re: [Python-projects] pylint #4581 proposed fix

2010-03-17 Thread Maarten ter Huurne
On Tuesday 16 March 2010, Donovan Lee Wanhoy wrote: > Attached is .diff file on a proposed fix for pylint #4581: option to NOT > get a Missing docstring (C0111) warning if a method is overridden. This sounds like a useful feature. > All I did was: > - add an option, no-docstring-overridden that