[code-quality] Bad coding style?

2014-02-07 Thread Thomas Heller
I sometimes have code like this: class Foo: def spam(self): from somewhere import method from somewhere import CONSTANT def blah(self): where CONSTANT defines a class attribute, anbd method is a method that I would like to call like any other methor (

Re: [code-quality] [Python-projects] New warning about print parens not a good idea?

2014-02-07 Thread Sasha Hart
If there are many people who actually want to enforce the non-use of print(arg) in 2.x for some specific reason, and not just because it is bad style to write if (a == b) or foobar((2)) - then I would strongly prefer for an error code to disable this check independently of the other useful warnings

Re: [code-quality] [Python-projects] New warning about print parens not a good idea?

2014-02-07 Thread Marc 'BlackJack' Rintsch
On 07/02/14 20:15, Sasha Hart wrote: > If there are many people who actually want to enforce the non-use of > print(arg) in 2.x for some specific reason, and not just because it is > bad style to write if (a == b) or foobar((2)) - then I would strongly > prefer for an error code to disable this che

Re: [code-quality] Bad coding style?

2014-02-07 Thread Ned Batchelder
On 2/6/14 1:51 PM, Thomas Heller wrote: I sometimes have code like this: class Foo: def spam(self): from somewhere import method from somewhere import CONSTANT def blah(self): where CONSTANT defines a class attribute, anbd method is a method that I w