Auto Run Python Scripts not working #63665

New Issue

Tom Wilson · 2019-04-16T20:47:47+02:00

Tom Wilson commented

2019-04-16 20:47:47 +02:00

Blender Version
Broken: blender-2.80.0-git.9099305771ec
Worked: 2.79

I have Auto Run Python Scripts enabled, Excluded Paths: empty.
I load the python file (named autorun.py) externally into the script editor and tick Register.
On loading the blend file however it simply doesn't run, I have to Alt-P it every time.
It's not throwing any errors, just to make sure I've tried with a python file consisting of print("HELLO"), but it never greets me :(
I've tried saving the file internally, Reloading it with Alt-R, absolutely nothing works.
Is this a bug or has something changed between 2.79 and 2.8 that I'm not aware of?

**Blender Version** Broken: blender-2.80.0-git.9099305771ec Worked: 2.79 I have Auto Run Python Scripts enabled, Excluded Paths: empty. I load the python file (named autorun.py) externally into the script editor and tick Register. On loading the blend file however it simply doesn't run, I have to Alt-P it every time. It's not throwing any errors, just to make sure I've tried with a python file consisting of print("HELLO"), but it never greets me :( I've tried saving the file internally, Reloading it with Alt-R, absolutely nothing works. Is this a bug or has something changed between 2.79 and 2.8 that I'm not aware of?

Tom Wilson commented

2019-04-16 20:47:47 +02:00

Added subscriber: @hedgehog90-3

Tom Wilson commented

2019-04-16 22:14:55 +02:00

Sorry, I was at fault. It's working fine.

EDIT:
Reopened, not sure if it's a bug, but I realised name equals the script name on startup (ie, if it's called run.py, it'll equal "run"), but equals "main" the rest of the time.
So the following never fires on startup:

if __name__ == "__main__":
	register()

Seems like a bug, can't find any mention of this elsewhere.

Sorry, I was at fault. It's working fine. EDIT: Reopened, not sure if it's a bug, but I realised __name__ equals the script name on startup (ie, if it's called run.py, it'll equal "run"), but equals "__main__" the rest of the time. So the following never fires on startup: ``` if __name__ == "__main__": register() ``` Seems like a bug, can't find any mention of this elsewhere.

Tom Wilson commented

2019-04-16 22:15:55 +02:00

Changed status from 'Open' to: 'Archived'

Tom Wilson closed this issue

2019-04-16 22:15:55 +02:00

Tom Wilson commented

2019-04-16 22:36:24 +02:00

Changed status from 'Archived' to: 'Open'

Tom Wilson reopened this issue

2019-04-16 22:36:24 +02:00

Jacques Lucke commented

2019-04-17 13:53:39 +02:00

Added subscribers: @ideasman42, @JacquesLucke

Jacques Lucke commented

2019-04-17 13:53:39 +02:00

Hm, not sure if this is a bug or intentional. Maybe @ideasman42 knows.

Sebastian Parborg commented

2019-04-17 14:38:09 +02:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-04-17 14:38:09 +02:00

Unless this has changed, then this is how it is supposed to work: https://www.geeksforgeeks.org/name-special-variable-python/

On startup, the file is run by an other python module and thus the __name__ can not be __main__.

Unless this has changed, then this is how it is supposed to work: https://www.geeksforgeeks.org/__name__-special-variable-python/ On startup, the file is run by an other python module and thus the `__name__` can not be `__main__`.

Jacques Lucke commented

2019-04-17 14:40:16 +02:00

Well, technically, when you run the script using the "Run" button, it is not __main__ either.

Well, technically, when you run the script using the "Run" button, it is not `__main__` either.

Stephen Swaney commented

2019-04-17 16:50:56 +02:00

Added subscriber: @StephenSwaney

Stephen Swaney commented

2019-04-17 16:50:56 +02:00

In #63665#662188, @JacquesLucke wrote:
Well, technically, when you run the script using the "Run" button, it is not __main__ either.

At the risk of looking even stupider than usual, who is running the script when you press "Run"?

I can see an argument for 'run at startup' vs 'press Run' being two separate use cases. It is not clear how to reconcile them. But if you want a quick hack...

if __name__ == '__main__' or __name__ == 'foo':

> In #63665#662188, @JacquesLucke wrote: > Well, technically, when you run the script using the "Run" button, it is not `__main__` either. At the risk of looking even stupider than usual, who *is* running the script when you press "Run"? I can see an argument for 'run at startup' vs 'press Run' being two separate use cases. It is not clear how to reconcile them. But if you want a quick hack... ``` if __name__ == '__main__' or __name__ == 'foo': ```

Campbell Barton commented

2019-04-18 15:04:23 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2019-04-18 15:04:23 +02:00

Campbell Barton self-assigned this 2019-04-18 15:04:23 +02:00

Campbell Barton commented

2019-04-18 15:04:23 +02:00

This was working as intended, however it added quite a lot of overhead to support importing text blocks as modules. Removed this feature, now "Run" and "Register" work the same way.

dc8dd24351

This was working as intended, however it added quite a lot of overhead to support importing text blocks as modules. Removed this feature, now "Run" and "Register" work the same way. dc8dd24351

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Auto Run Python Scripts not working #63665