Timeline for Cannot import nested Python module when writing an add-on
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2021 at 0:55 | comment | added | michael_vendler | Thank you for the comments! I was able to solve it by diving down the rabbit hole provided by @scurest. I created a function to register my add-on path with Blender's paths, moved my class imports to a getter function, and called these from my own register/unregister functions instead of using Blender's factory utility. | |
| Feb 23, 2021 at 6:49 | comment | added | batFINGER | (Not using VS) but suggest looking at answers here blender.stackexchange.com/questions/158775/… and similarly here blender.stackexchange.com/questions/183773/… Rather than some horrible long import chain to get a blender class to register, can propagate the register down the hierarchy by calling the register method of immediate child modules. | |
| Feb 23, 2021 at 1:17 | comment | added | scurest |
See this. Everyone just writes from . import though. You can always check how the default addons do things.
|
|
| Feb 23, 2021 at 0:51 | review | First posts | |||
| Feb 23, 2021 at 4:45 | |||||
| Feb 23, 2021 at 0:48 | history | asked | michael_vendler | CC BY-SA 4.0 |