Re: Global Python interpreter?

[Sergio Mucino]

Thanks Raffaele. Yes, in both applications I've used (Maya and Max) this is how it works. Any functions and variables I declare or define at the global scope remain in memory throughout the session. This makes it very easy to iterate over different version of tool development. It seems SI won't be as user-friendly in the same department (Modo used to be like that, but they just released a Python API with 7.1 that allows for a persistent interpreter, which solves the same problem). Given that this is one of those things I can't really work around, I'll just consider it as a little "would be really nice to address" note for the Softimage team. Thanks a lot for all the comments! On 20/10/2013 5:44 PM, Raffaele Fragapane wrote: I might have been unclear, sorry. No, it won't work across tabs of course, but it gets closer to Maya's way of working within each tab (which I understand is where Sergio comes from), and it allows to expand or contract module functionality on the fly. For it to work across different interpreters yes, you need to extend it with some files, a directory parser, and a push to dir wrapper to extend the magic module. On Sat, Oct 19, 2013 at 2:46 AM, Luc-Eric Rousseau <luceri...@gmail.com> wrote: On Thu, Oct 17, 2013 at 6:22 PM, Raffaele Fragapane <raffsxsil...@googlemail.com> wrote: > If you want something to be available across the board you can simply write > it, register it as a module, and push it. No need for it to exist as a file. I've read the link, but I can't see how you could use this to push functions to a different instance of the python interpreter without using some file on disk (or copy/pasting the code between script editor tabs) -- Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!