As always, thank you very much for the unselfish sharing of your knowledge @c.poupin ,
But I am completely confused now:
The way I work is, I click on Run/Executer, and close the Python node dialog. If I open the Python node dialog, my code changes have been saved, even though I never click on the ‘Save’ button.
Imagine writing a bunch of code, and you get to a point where ‘this bit is good, but I want to do even more.’ Instead of having to close the window, then save the graph, this allows you to save with the editor open, then save the graph. It also enables switching the Python engine being used.
Thank you for the reply @jacob.small ,
Maybe I formulated my question wrongly.
At the moment, the following is possible to be done in the Python node: one writes a code, and clicks on ‘Run’ button inside the Python node. Then closes the Python node editor window. Opens it again, and all the code I wrote is there, even though I didn’t use the ‘Save’ button inside the Python node editor.
It seems, the only purpose this ‘Save’ button serves, is to enable switching between IronPython2 and CPython3 engines.