Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <544c90c6$0$12986$c3e8da3$5496439d@news.astraweb.com>
References: <rr4g4ah01n2efganet7b8oml8uq1qaf9qc@4ax.com> <mcll4adnnt307a37p03dlhqq9bmskf2qll@4ax.com> <185ea3d5-71d3-4009-8afe-4f0c2b6bbf30@googlegroups.com> <viol4al91s5e1k7nb6hhdo08hc5k0d82em@4ax.com> <e80c48b8-ab00-4d6c-9bfa-bdacfdac0dbb@googlegroups.com> <25c6a468-e596-4a31-856b-bb5fe22c8894@googlegroups.com> <mailman.15156.1414211150.18130.python-list@python.org> <9dd6db37-5568-405e-8af7-3a28195eec4d@googlegroups.com> <mailman.15158.1414216160.18130.python-list@python.org> <544c90c6$0$12986$c3e8da3$5496439d@news.astraweb.com>
Date: Sun, 26 Oct 2014 17:42:06 +1100
Subject: Re: Side-effects [was Re: I am out of trial and error again Lists]
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.15190.1414305729.18130.python-list@python.org>
Lines: 37
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:79706

On Sun, Oct 26, 2014 at 5:12 PM, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> wrote:
> However, mutator methods on a class don't change global state, they change
> the state of an instance. Even random.random and friends don't change
> global state, they change a (hidden) instance, and you can create your own
> instances when needed. That gives you the convenience of pseudo-global
> state while still allowing the flexibility of having separate instances.
> Even global variables in Python are global to the module, not global to the
> entire application.

True, but they do still change state; I oversimplified a bit, but
certainly there are plenty of functions that change state in some way,
and are not frowned upon.

Module level variables really are global, though. You can't easily and
conveniently reinstantiate a module in Python; if you "import random;
random.seed(1234)", you can confidently expect that some other module
that uses random.random will be affected. Sure, there are ways around
that, but that's true of any form of global state - for a start, it's
usually "process level" state, in that spawning a new process will
isolate one from another. The only thing that isn't truly global is
the namespace; I can write "x = {}" and you can write "x = []" and
they don't collide. They're still global (process-level), it's just
that they're "foo.x" and "bar.x" and are thus distinct.

> I would say that Python is a pragmatic
> language which uses whatever idiom seems best at the time, but over all it
> prefers mutable state for compound objects, prefers immutable state for
> scalar objects (like numbers), and discourages the unnecessary use of
> global mutable state.

It's not really compound vs scalar, but yes, I agree. Practicality
beats purity, on so many levels. Functions with side effects aren't
considered some sort of weird beast that we have to permit for the
sake of I/O; they're a fundamental part of the language.

ChrisA