Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.datemas.de!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail From: Marco Buttu Newsgroups: comp.lang.python Subject: Re: class-private names and the Zen of Python Date: Tue, 08 Oct 2013 12:47:17 +0200 Organization: Aioe.org NNTP Server Lines: 23 Message-ID: <5253E2B5.4060905@gmail.com> References: NNTP-Posting-Host: yLEXU8HhfLiiXyuXjVRTFQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.python:56385 On 10/08/2013 12:36 PM, Terry Reedy wrote: > On 10/8/2013 6:13 AM, Marco Buttu wrote: >> In the following case: >> >> >>> class Foo: >> ... _Foo__a = 100 >> ... __a = 33 >> ... >> >>> Foo._Foo__a >> 33 >> >> I think this behavior, for a user who does not know the convention, >> could be a surprise. > > No one qualified to use such names would do such a thing , so there is > no need to worry about it or do anything about it. Is this transformation performed by the parser, before to call the metaclass? -- Marco Buttu