Thanks for the quick answer! I tried to file a ticket, but I couldn't register to the site, and couldn't figure out how to do it anonymously...
________________________________ From: Sylvain Thénault <[email protected]> To: Yoni Tsafir <[email protected]> Cc: [email protected] Sent: Wed, October 20, 2010 6:18:33 PM Subject: Re: pylint bug - E1101 & E0102 upon use of @property + @foo.setter On 20 octobre 09:11, Yoni Tsafir wrote: > Hello, Hi, please use the [email protected] mailing list to discuss about pylint (CCed). > 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). > Is there a workaround for that without having to change the code? I don't > want > to disable the errors as they are important for other places. I don't see any workaround beside explicitly disabling the message using "pylint: disable=..." on the hurting line. Would you please file a ticket for this on the pylint's tracker? -- Sylvain Thénault LOGILAB, Paris (France) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
