Commit b0f7fa1d authored by Miss Islington (bot)'s avatar Miss Islington (bot) Committed by GitHub

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


Initial patch by Chandan Kumar.
(cherry picked from commit 13ae4d44)
Co-authored-by: default avatarBerker Peksag <berker.peksag@gmail.com>
parent 2546ac8e
...@@ -651,6 +651,11 @@ breaking intraclass method calls. For example:: ...@@ -651,6 +651,11 @@ breaking intraclass method calls. For example::
for item in zip(keys, values): for item in zip(keys, values):
self.items_list.append(item) 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 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 possible to access or modify a variable that is considered private. This can
even be useful in special circumstances, such as in the debugger. even be useful in special circumstances, such as in the debugger.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment