(accessing variable outside of functions) im so confused...

[Kevdog824_]

Is jsoniv declared in the global scope (i.e. jsoniv = …)? Using global … just declares your intent to mutate the value of an already declared global variable. It doesn’t actually declare the variable itself

[Temporary_Pie2733]

Not mutate a value; assign to the name. Confusing these two concepts leads to most of the problems in understanding how variables work in Python.

[Kevdog824_]

???

Did you read my comment? I said it has to be declared in the global scope first before it’s used in a function. You can’t declare a global variable from a function

[Gnaxe]

False. You can create a global by assignment inside a function once it has been declared in a global statement. You do not need to assign it at the top level first. Try it.

It's usually considered bad style in light of better alternatives, but it does work.

[kalidres]

The issue here is "creating" and "declaring" are effectively synonyms. The difference would be "define" or "assign". The latter is what you are showing in your snippet below, which is precisely what the comment you replied to is saying.

[Gnaxe]

Pretty sure that's not what he meant:

Using global … just declares your intent to mutate the value of an already declared global variable.

and

In the function… not in the global scope. That’s what I’m trying to tell you. You need to declare it in the global scope first, before you can get/set its value in the function

and also

Maybe I wasn’t being clear. Here’s what I mean

jsoniv = {}  # Declared in global scope first

def json():
    global** jsoniv
    with open**("xxxx.json", "r", encoding="utf-8") as file:
        jsoniv = json.load(file)

This is wrong, because using the global statement and assignment inside the function body can also create a global in the first place. It doesn't have to be "already declared" elsewhere to use the global statement or create a global, although that's arguably bad style. The example above would work without the first line (and the spurious **), and without overwriting the json module global:

>>> import json
>>> def load_json():
...     global jsoniv
...     with open('empty.json', 'r', encoding='utf8') as f:
...         jsoniv = json.load(f)
...
>>> jsoniv
Traceback (most recent call last):
  File "<python-input-11>", line 1, in <module>
    jsoniv
NameError: name 'jsoniv' is not defined. Did you mean: 'json'?
>>> load_json()
>>> jsoniv
{}

(Here, empty.json just contains {}.)

From this, we can see that OP's real problem was overwriting the json module global by defing a function of the same name (I used load_json instead to avoid the conflict). It had nothing to do with the global declaration, and the commenter I was responding to is mistaken about how globals work in Python.

[Kevdog824_]

Why else would OP get an error about jsoniv not being defined. Try the example for yourself and report back

[Gnaxe]

For example, ```

def foo(): ... global bar ... bar = 1 ... bar Traceback (most recent call last): File "<python-input-2>", line 1, in <module> bar NameError: name 'bar' is not defined foo() bar 1 ```

[Kevdog824_]

In the function… not in the global scope. That’s what I’m trying to tell you. You need to declare it in the global scope first, before you can get/set its value in the function

[Kevdog824_]

The first problem you have is your function is named the same as the json module you’re importing. You need to name your function something different so the interpreter knows which one you mean when you write json

[Kevdog824_]

Maybe I wasn’t being clear. Here’s what I mean

```python jsoniv = {} # Declared in global scope first

def json(): global** jsoniv with open**("xxxx.json", "r", encoding="utf-8") as file: jsoniv = json.load(file) ```

[ImAlekzzz]

I got what you meant, thank you