Hi all,
Thank you for the feedback. So, to recap, reasons to use name mangling
'self.__update(iterable)' rather than qualified access
'Mapping.update(self, iterable)' are:
1. Qualified access stops working when class 'Mapping' is renamed
(at compile-time) or its name is reassigned at runtime.
H
On Wed, 14 Dec 2016 07:27 am, paoli...@gmail.com wrote:
> The official Python tutorial at
>
> https://docs.python.org/3/tutorial/classes.html#private-variables
>
> says that "name mangling is helpful for letting subclasses override
> methods without breaking intraclass method calls" and makes an
paoli...@gmail.com writes:
> The official Python tutorial at
>
> https://docs.python.org/3/tutorial/classes.html#private-variables
>
> says that "name mangling is helpful for letting subclasses override methods
> without breaking intraclass method calls" and makes an interesting example:
>
> clas
On 13Dec2016 12:27, paoli...@gmail.com wrote:
The official Python tutorial at
https://docs.python.org/3/tutorial/classes.html#private-variables
says that "name mangling is helpful for letting subclasses override methods without
breaking intraclass method calls" and makes an interesting example
The official Python tutorial at
https://docs.python.org/3/tutorial/classes.html#private-variables
says that "name mangling is helpful for letting subclasses override methods
without breaking intraclass method calls" and makes an interesting example:
class Mapping:
def __init__(self, iterabl
