On Tue, Jan 22, 2019 at 6:33 PM Stephan Reiter <stephan.rei...@gmail.com> wrote: > > Thanks for the answers so far. I appreciate them! > > Nathaniel, I'd like to allow Python plugins in my application. A > plugin should be allowed to bring its own modules along (i.e. > plugin-specific subdir is in sys.path when the plugin is active) and > hence some isolation of them will be needed, so that they can use > different versions of a given module. That's my main motivation for > using subinterpreters. > I thought about running plugins out-of-processes - a separate process > for every plugin - and allow them to communicate with my application > via RPC. But that makes it more complex to implement the API my > application will offer and will slow down things due to the need to > copy data. > Maybe you have another idea for me? :)
Not really, sorry! I believe that most applications that support Python plugins (like blender, gimp, libreoffice, etc.), do it by using a single shared environment for all plugins. This is also how every application written in Python works, so at the ecosystem level there's a lot of pressure on module authors to make it possible to assemble them into a single coherent environment. -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
