Can you elaborate on that use case? Which two applications are you thinking of, and what was your goal in driving them? This sounds interesting but I haven’t encountered this myself.
On Fri, Jun 18, 2021 at 09:44 Baptiste Carvello < [email protected]> wrote: > Le 18/06/2021 à 08:50, Paul Moore a écrit : > > > > IMO it doesn't. However for certain applications (the sort of thing I > > was referring to) - where the user is writing their own scripts and > > the embedding API is used merely to expose an interface to the Python > > language, dynamically linking to whatever version of Python the user > > has installed can be precisely the right thing to do - the user gets > > access to the version of the language they expect, the installed > > packages they expect to see, etc. > > As a user, I second this. When trying to drive applications from the > outside (as opposed to extending them through plugins), it is annoying > when two applications won't work together because each one insists on > using its own vendored python. > > Of course, there are often real blockers, such as incompatible event > loops. But not always… > > Cheers, > Baptiste > _______________________________________________ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/PPKL7466BIG6DPCUIJURLE5ZGFNHBNSM/ > Code of Conduct: http://python.org/psf/codeofconduct/ > -- --Guido (mobile)
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/U34DJD6TKP3LMDBLZ77JHQYHU6SKIADU/ Code of Conduct: http://python.org/psf/codeofconduct/
