The right way to 'call' a class attribute inside the same class
Chris Angelico
rosuav at gmail.com
Tue Dec 13 01:05:13 EST 2016
On Tue, Dec 13, 2016 at 4:45 PM, Steven D'Aprano
<steve+comp.lang.python at pearwood.info> wrote:
> I don't understand the point of bringing up Javascript. Ben has already said
> that we shouldn't feel the need to mindlessly copy C++ terminology. Is it your
> position that we *should* copy Javascript terminology? Why Javascript and not
> C++ or ObjectiveC? Even when it goes against the obvious English mnemonic?
I'm saying that ALL these terminology debates are needlessly pedantic.
Whatever word you use, you're going to have to explain the Python
semantics as distinct from everyone else's, so don't sweat it. Whether
we call __init__ the constructor or initializer, there is going to be
someone out there who misinterprets it. Go with whatever, pick the
easiest to explain (which is probably "__new__ is allocator, __init__
is initializer"), and don't try to burden the terms alone with the job
of explaining Python's semantics.
ChrisA
More information about the Python-list
mailing list