Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #29394 > unrolled thread

Re: how to use property?

Started byTerry Reedy <tjreedy@udel.edu>
First post2012-09-17 19:34 -0400
Last post2012-09-17 19:34 -0400
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: how to use property? Terry Reedy <tjreedy@udel.edu> - 2012-09-17 19:34 -0400

#29394 — Re: how to use property?

FromTerry Reedy <tjreedy@udel.edu>
Date2012-09-17 19:34 -0400
SubjectRe: how to use property?
Message-ID<mailman.845.1347924911.27098.python-list@python.org>
On 9/17/2012 6:12 PM, Chris Angelico wrote:
> On Tue, Sep 18, 2012 at 7:55 AM, Fernando Jiménez <the.merck@gmail.com> wrote:
>> Hi guys!
>>
>> I'm noob in python and I would know how to correctly use the property. I
>> have read some things about it but I do not quite understand.
>>
>> But I think it's a bad habit to use _ to change the visibility of the
>> attributes as in JAVA.
>>
>> How to correctly use the property?
>
> The single leading underscore is nothing to do with visibility; it's a
> courteous request that external referents not touch something. In a
> "consenting adults" model, that's usually sufficient.
>
> For the most part, in fact, you don't need @property at all. Just make
> an object's members public and save yourself the trouble! Unlike the
> recommendation in C++ and Java, Python doesn't ask you to hide things
> and write code to make them available. Instead of starting with
> getters and setters, just start with a flat property, and move to
> getters/setters only when you find you need them.

More examples:

A class has a data attribute that really is a simple attribute, no 
property. You define a subclass that needs a calculation for the 
attribute. So you use property in the subclass.

A class has an attribute that is a constant that must be computed. You 
do not want to compute is unless and until needed.

def get_x(self):
   try:
     return self._x
   except AttributeError:
     self._x = calculate_x()
     return self._

For a read-only attribute, don't provide a setter. If you do not like 
"AttributeError: can't set attribute", provide one with a customized error.

But I think most of the data attributes in stdlib classes are straight 
attributes.

-- 
Terry Jan Reedy

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web