Ezio Melotti <ezio.melo...@gmail.com> added the comment:

I think the main problem here is that they are called "private" and people 
coming from other languages assume that the double underscore is the Python way 
to mark variables as private, whereas the appearance of being private is just a 
side effect of the name mangling.

This part should IMHO focus on the name mangling, explaining what it is and 
what it's useful for, and mention clearly that this doesn't really make the 
variable "private", because it can still be accessed through the mangled name.

The section could also mention that the word "private" here doesn't mean the 
same thing as in other language.

I don't know if the "trust the programmer" philosophy found in Python is 
explained somewhere in the doc, but if not it could be added to the tutorial or 
the FAQ.

----------
nosy: +ezio.melotti, rhettinger

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12086>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to