traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

bpo-21196: Clarify name mangling rules in tutorial (GH-5667) 

Initial patch by Chandan Kumar.
(cherry picked from commit 13ae4d4438)

Co-authored-by: Berker Peksag <berker.peksag@gmail.com>
This commit is contained in:
Miss Islington (bot) 2018-10-19 17:41:56 -07:00 committed by GitHub
parent c8348fb6d2
commit 3e5bcd12f6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Doc/tutorial/classes.rst
View File

@ -703,6 +703,11 @@ breaking intraclass method calls. For example::
for item in zip(keys, values):
self.items_list.append(item)
The above example would work even if ``MappingSubclass`` were to introduce a
``__update`` identifier since it is replaced with ``_Mapping__update`` in the
``Mapping`` class and ``_MappingSubclass__update`` in the ``MappingSubclass``
class respectively.
Note that the mangling rules are designed mostly to avoid accidents; it still is
possible to access or modify a variable that is considered private. This can
even be useful in special circumstances, such as in the debugger.