On 7 June 2013 09:32, Skip Montanaro <s...@pobox.com> wrote: > > Correct, but I would just like to be alerted that perhaps I should > consider narrowing my API. Some of the code base I work on was around > before Python 2.2 was available. Over time, people have started to > add property-based setters and getters. In many circumstances, we > should probably pick one way to do it, in this case self.foo vs > self.get_foo(). I'm just looking for the message to remind me to > consider the API duplication. I'm not suggesting pylint or other > tools should recommend one or the other.
That makes sense. You could do something similar when people are migrating methods but the old one's hanging around. -- Martin
_______________________________________________ code-quality mailing list code-quality@python.org http://mail.python.org/mailman/listinfo/code-quality
