Comments on: About getters and setters in Python http://unclezeiv.kerid.org/2009/08/about-getters-and-setters-in-python frequently lost in thought Wed, 24 Mar 2010 01:34:57 +0000 hourly 1 http://wordpress.org/?v=3.0 By: UncleZeiv http://unclezeiv.kerid.org/2009/08/about-getters-and-setters-in-python/comment-page-1#comment-3846 UncleZeiv Thu, 27 Aug 2009 22:41:59 +0000 http://unclezeiv.kerid.org/?p=91#comment-3846 <a href="#comment-3842" rel="nofollow">@PJ Eby</a> Interesting solution, it didn't occur to me... it could indeed solve my problems. (Thanks for commenting, I really appreciated it.) @PJ Eby
Interesting solution, it didn’t occur to me… it could indeed solve my problems.

(Thanks for commenting, I really appreciated it.)

]]> By: PJ Eby http://unclezeiv.kerid.org/2009/08/about-getters-and-setters-in-python/comment-page-1#comment-3842 PJ Eby Thu, 27 Aug 2009 14:09:14 +0000 http://unclezeiv.kerid.org/?p=91#comment-3842 If the properties aren't performance-critical, you can always make the property in the base class be property(lambda s:s.get_foo(), lambda s,v: s.set_foo(v)). Then, simply override the getter or setter in the subclass(es) involved. In any case, there are plenty of worse ways that changes to a base class can impact a subclass; subclassing is inherently a tighter coupling between classes than mere use. If the properties aren’t performance-critical, you can always make the property in the base class be property(lambda s:s.get_foo(), lambda s,v: s.set_foo(v)). Then, simply override the getter or setter in the subclass(es) involved.

In any case, there are plenty of worse ways that changes to a base class can impact a subclass; subclassing is inherently a tighter coupling between classes than mere use.

]]>