Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: jmp <jeanmichel@sequans.com>
Newsgroups: comp.lang.python
Subject: Re: Encapsulation in Python
Date: Fri, 11 Mar 2016 17:42:49 +0100
Lines: 48
Message-ID: <mailman.27.1457714598.26429.python-list@python.org>
References: <56E17985.7060002@benmezger.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
In-Reply-To: <56E17985.7060002@benmezger.nl>
Precedence: list
Xref: csiph.com comp.lang.python:104624

On 03/10/2016 02:41 PM, Ben Mezger wrote:
> Hi all,
>
> I've been studying Object Oriented Theory using Java. Theoretically, all
> attributes should be private, meaning no one except the methods itself
> can access the attribute;
>
> public class Foo {
>      private int bar;
>      ...
>
> Normally in Java, we would write getters and setters to set/get the
> attribute bar. However, in Python, we normally create a class like so;
>
> class Foo(object):
>      bar = 0
>      ...
>
> And we usually don't write any getters/setters (though they exist in
> Python, I have not seen much projects making use of it).
>
> We can easily encapsulate (data hiding) Foo's class using the '_'
> (underscore) when creating a new attribute, however, this would require
> all attributes to have a underscore.
> According to this answer [1], it's acceptable to to expose your
> attribute directly (Foo.bar = 0), so I wonder where the encapsulation
> happens in Python? If I can access the attribute whenever I want (with
> the except of using a underscore), what's the best way to encapsulate a
> class in Python? Why aren't most of the projects not using
> getters/setters and instead they access the variable directly?
>
> Regards,
>
> Ben Mezger

Strictly speaking there is not such things as public/private attributes 
in python. All attributes are public.

'_' is just a (good) convention to tell the class users "don't mess with 
this attribute, don't read it nor write it".

And the python way is to stick to this, trust your users to not use your 
'private' attributes they've been warned.

Short story : in Python we don't hide, we flag.

JM