Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!not-for-mail
From: Chris Angelico <rosuav@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: A newbie quesiton: local variable in a nested funciton
Date: Sun, 27 Dec 2015 17:32:17 +1100
Lines: 43
Message-ID: <mailman.27.1451197940.11925.python-list@python.org>
References: <d070aa0d-e80f-4efb-a424-351737ddb2fc@googlegroups.com> <mailman.17.1451101449.11925.python-list@python.org> <701dd0e6-a9c1-4aa9-a3a2-6607cd3f3759@googlegroups.com> <mailman.19.1451123395.11925.python-list@python.org> <661a13a1-8084-41ca-b458-297462dc3367@googlegroups.com> <0bf611ba-c4d9-4465-8d61-6a94bcee79a4@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <0bf611ba-c4d9-4465-8d61-6a94bcee79a4@googlegroups.com>
Precedence: list
Xref: csiph.com comp.lang.python:100903

On Sun, Dec 27, 2015 at 3:11 PM,  <jfong@ms4.hinet.net> wrote:
> Last night I noticed that Python does not resolve name in "def" during im=
port, as C does in the compile/link stage, it was deferred until it was ref=
erenced (i.e. codes was executed). That's OK for Anyway codes has to be deb=
ugged sooner or later. I just have to get used to this style.
>
> But check these codes, it seems not.
> -------
> x =3D 1  # a global variable
> print(x)
>
> class Test:
>     x =3D 4  # a class attribute
>     print(x)
>     def func(self):
>         print(x)
>
> x1 =3D Test()
> x1.x =3D 41  # a instance's attribute
> x1.func()  # it's 1 but 41 was expect:-(
> --------
>
> --Jach

When you import this module, it runs all top-level code. So the
'print' at the top will happen at import time.

Among the top-level statements is a class definition. When that gets
run (to construct the class itself - distinct from instantiating it,
which happens further down), it builds a class by executing all the
statements in it, in order. That results in that value of x being
printed, and then defines a function.

The function definition is being run at time of class construction,
and it creates a new attribute on the Test class. At that time, the
function body isn't actually executed (as you might expect). However,
it's worth noting that the function does not inherit class scope. The
unadorned name 'x' references the global. If you want to access
class-scope names from inside methods, you need to say 'self.x', which
also applies to instance attributes. That's what would do what you
expect here.

ChrisA