accessing globals from a function

[Skaperen]

normally a function only has read-only access to global variables. in order to update a global variable the code must declare which variable names it will access using the global statement. i am finding that if i initially make these variables be mutable container types such as list or dictionary, i can update the container contents without a global statement. so, instead of doing:

1 2 3 4 5 6

counter = 0 ... def increment():     global counter     counter += 1     return

i could do:

1 2 3 4 5

counter = [0] ... def increment():     counter[0] += 1     return

is this safe to do? if not, why not?

[Mekire]

You only need the global keyword to assign to the name.
You can always access and mutate globals without it.
The second one is mutable, so yeah, it works.

As to whether it is safe, I suppose. It is as safe as any other method of mutatating a global. Both methods are horrible and shouldn't be used unless absolutely necessary.

Pretty much the only use case I encourage for the global keyword is writing a function that creates the global object which, from that point on, will be considered constant everywhere else. For instance I load graphics in a function in pygame as they can't be loaded until some initialization is done but I still want them accessible everywhere. They are created as global but are never again altered.

[Skaperen]

i do agree using global where not necessary is a bad thing. but where it is necessary, how would you choose to do it between the 2 examples i gave?

[Gribouillis]

There is a third way

1 2 3 4 5

glo = type('glo', (), {})() glo.counter = 0   def increment():     glo.counter += 1

You can even do this

1 2 3 4 5 6 7 8 9 10 11

>>> glo = type('glo', (), {})() >>> glo.__dict__ = globals() >>> counter = 0 >>> def increment(): ...     glo.counter += 1 ... >>> increment() >>> increment() >>> increment() >>> counter 3

[DeaD_EyE]

I prefer the 'third' (Gribouillis) way.
He made a class. Here the same not in compact form with an __iter__ method:

1 2 3 4 5 6 7 8 9 10 11

class Count:       def __init__(self, start=0):         self.counter = start       def increment(self):         self.counter += 1         return self.counter     def __iter__(self):         while True:             yield self.increment()

Somewhere you create an instance of Counter and then you can assign to instance.counter.
My first reaction, if I see a global, can I do this with a class. The benefit is, that I can control the behavior with the magic methods. For example this implementation allows iteration. The class itself is an Iterator. You can also protect attributes in the class with @property. You can have also class-attributes, for example to see how much instances of Counter has been created.

[snippsat]

A modern count

1 2 3 4 5 6 7 8 9

from dataclasses import dataclass   @dataclass class Counter:     counter: int = 0       def __call__(self):         self.counter += 1         return self.counter

1 2 3 4 5 6 7 8 9 10 11

>>> count = Counter() >>> count() 1 >>> count() 2 >>> count() 3 >>> count Counter(counter=3) >>> count.__annotations__ {'counter': <class 'int'>}

[Skaperen]

lots of ways!

you need to develop a function. while designing it you realize it needs to remember something from a previous call. which of these ways would you use? would you need to start all over with the design or would you adapt what you have done so far? yeah i know; sorry that's so vague.

[Gribouillis]

while designing it you realize it needs to remember something from a previous call. which of these ways would you use?

I would immediately turn the function into a method of a class.

That said, there are nice alternatives. I sometimes use the following trick

1 2 3 4 5 6 7 8 9

class Static:     def __init__(self, *args, **kwargs):         self.__dict__.update(*args, **kwargs)   def myfunc(static=Static(counter=0)):     static.counter += 1     return static.counter   print(myfunc(), myfunc(), myfunc()) # prints 1 2 3

[Skaperen]

what if you are trying to implement a function for some very large program that calls it as a function in thousands of places all over its code?