Path: csiph.com!usenet.pasdenom.info!dedibox.gegeweb.org!gegeweb.eu!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!nerim.net!novso.com!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
To: python-list@python.org
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject: Re: [Newbie] Require help migrating from Perl to Python 2.7 (namespaces)
Date: Tue, 25 Dec 2012 16:04:01 -0500
Organization: > Bestiaria Support Staff <
References: <mailman.1225.1356296379.29569.python-list@python.org> <roy-52F25F.16151223122012@news.panix.com> <3f14f739-e660-4883-a940-c77a6092cb79@googlegroups.com> <mailman.1240.1356326385.29569.python-list@python.org> <bdd3b0ba-acc6-4bf7-9e2d-a71f1858b361@googlegroups.com> <mailman.1255.1356364135.29569.python-list@python.org> <f0f7b480-fd48-4634-87df-4e026501357b@h2g2000yqa.googlegroups.com> <928f93e9-8ade-47a1-968d-63af0889b104@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.1273.1356469450.29569.python-list@python.org>
Lines: 63
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:35497

On Tue, 25 Dec 2012 04:55:06 -0800 (PST), prilisauer@googlemail.com
declaimed the following in gmane.comp.python.general:

> Hey :-P I think I should rename the threads name into a new "Doc" project, 
> I'm sure It won't take much time to fill a book with our knowledge. 
> 
> Thanks to Rick, you have Posted exactly what I wanted to ask. I know the that 
> __variable = 'xyz'
> _variable = 'xyz'
> 
> are used to make them private, but I haven't found it for methods. Thanks :)
> 

	No... Single _ is a hint to the programmer using the name that it is
/considered/ "internal" and subject to change -- use at your own risk.

	Double __ invokes name-mangling so that one does not conflict with a
parent class method (when one does NOT want to override the parent
class' method with the subclass method). It's a weird, seldom used,
situation.

>>> class ABC(object):
... 	def __something(self):
... 		pass
... 	def notsomething(self):
... 		pass
... 	
>>> class XYZ(ABC):
... 	def __something(self):
... 		pass
... 	def notsomething(self):
... 		pass
... 	
>>> obj = XYZ()
>>> dir(obj)
['_ABC__something', '_XYZ__something', '__class__', '__delattr__',
'__dict__', '__doc__', '__format__', '__getattribute__', '__hash__',
'__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__',
'__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__',
'__weakref__', 'notsomething']
>>> 

	An instance of XYZ has two name-mangled __something methods, but
only one not mangled notsomething method.

	Inside methods of XYZ, any use of __something will invoke
_XYZ__something -- but it is possible to explicitly invoke the parent
_ABC__something if needed.



> I also don't think you're off topic! It's a big grey scale :-) and for me the first post till the last one is a part of my "question"
> 
> PEP, is nice, it tooks me a few days to get trough all your input and my code. Anyway is there also a best practice for naming? eg.: module_class_sub() or wording? eg.: socket: send() recv() -> recv is kept short. according PEP8??
> 
> 
> It seems, my english slowly getting better again, If my colleagues would see what I'm writting here they won't belive me. I've worked at the Pharmaceutical IT and made Codereviews and programming for medical software. I still can't belive what I've forgotton the last two years. But still PEP etc. isn't far that hard written like pharm eu, usp, and 21CFR. Shame on me, but I will come back, after I've finished.
> 
> BR
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
        wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/