Re: Potential pitfalls when going from old-style to new-style classes

2014-11-19 Thread Chris Kaynor
On Wed, Nov 19, 2014 at 11:14 AM, Skip Montanaro wrote: > I discussion on the code-quality list got me thinking. Suppose I have > an old-style class in a 2.x app: > > class Foo: > def __init__(self): > blah blah blah > > I still use 2.x exclusively, but anytime I run pylint over a bit of >

Re: Potential pitfalls when going from old-style to new-style classes

2014-11-19 Thread Ethan Furman
On 11/19/2014 11:14 AM, Skip Montanaro wrote: > I discussion on the code-quality list got me thinking. Suppose I have > an old-style class in a 2.x app: > > class Foo: > def __init__(self): > blah blah blah > > I still use 2.x exclusively, but anytime I run pylint over a bit of > code and i