Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!uio.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!nzpost1.xs4all.net!not-for-mail
MIME-Version: 1.0
In-Reply-To: <CALwzid=mehH8poQA=FoEaZXRhyGcAAMP+aKw-3O8+ymz8zwNNA@mail.gmail.com>
References: <c3363$547e74fe$5419aafe$24179@news.ziggo.nl> <4602a32c-5109-47dd-95bb-b9723738f07f@googlegroups.com> <CALwzid=mehH8poQA=FoEaZXRhyGcAAMP+aKw-3O8+ymz8zwNNA@mail.gmail.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Thu, 3 Sep 2015 13:51:56 -0600
Subject: Re: Python handles globals badly.
To: Python <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.95.1441309964.8327.python-list@python.org>
Lines: 22
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:95970

On Thu, Sep 3, 2015 at 1:47 PM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> On Thu, Sep 3, 2015 at 1:05 PM,  <tdev@freenet.de> wrote:
>
>> But then I ask you from high-level point of view
>> (if my high level view is correct at all):
>> Would you remove this keyword if it would be technically possible
>> or is good for you from high level point of view to have a keyword "global"?
>
> Provided that the proposal doesn't open up the possibility of
> unintentionally creating a global variable where I wanted a local, I'd
> be okay with it.

Let me clarify that I'd be okay with making the keyword optional. It
should probably still be kept around for the occasional use like this:

exec("""def function():
    global {0}
    {0} = 42
""".format('x'))

where the compiler would have little hope of figuring out that the
variable was meant to be global without it.