pylint #51222 using @foo.setter causes E1101 & E0102 [validation pending]
I noticed pylint doesn't handle well the case of: @property def foo(self): return self._bar.foo @foo.setter def foo(self, foo_val): self._bar.foo = foo_val Though it's a perfectly valid case syntax since python2.6 It says I defined foo twice, and doesn't understand the ".setter" syntax (Gives E1101 & E0102). | |
priority | normal |
---|---|
type | enhancement |
done in | 0.25.1 |
load left | 0.000 |
closed by | #869685f9a22d Do not issue warnings when using 2.6's property.setter/deleter functionality. Closes #50461, #52020 and #51222. |
Comments
-
2010/11/23 07:28
add commenthttp://stackoverflow.com/questions/3980038/pylint-bug-e1101-e0102-upon-use-of-property-foo-setter/4253707