[Cheiron]

the question is short and sweet:

what is difference between just declaring a global inside a script and declaring global in the field at top of script editor?
_________________
Cheiron
______________________________
"Any scientist with respect for himself should start
the day by rejecting his own pet hypotheses".
(Konrad Lorenz)

"Wir müssen wissen
Wir werden wissen"
(David Hilbert)

[Scotsman]

The short answer is scope. Yeah real helpful I know.

From Learning Python (O'Reilly publishers) page 104

The global statement is the only thing that's anything like a declaration in Python. It tells Python that a function plans to change global names -- names that live in the enclosing module's scope (namespace). We've talked about global in passing already; as a summary:

* global means "a name at the top-level of a module file."
* global names must be declared only if they are assigned in a function.
* global names may be referenced in a function without being declared.

Also there are several documents at http://www.python.org/doc/ that may be helpful.

[Bri]

always thought the global statement is used to allow access to a global variable, not to declare one.
_________________
RL..now with 100% less lag!

[Studio 12]

The other haft of the answer is.

I believe the global field at the top of the script editor is for delclaring a script "global" for the whole server. You have to enter the room which it resides in for it to load.
_________________
Never be afraid to try something new. Remember, amateurs built the ark, professionals built the Titanic.

[Scotsman]

So did I Bri, but apparently I was mistaken. Going to have to play with it a little bit now that had to go look up the info for Cheiron.

That's correct Studio, that field allows you to declare a module name to detach the script into so it is not purged from memory when you leave the room.

[Cheiron]