Brett Cannon wrote: > It's a discussion issue. PEP 554 is trying to focus on the API of > subinterpreters and doesn't want to distract from that by bringing the GIL > into it. > That being said, the general expectation from everyone involved is there > will be a perl-interpreter GIL. > On Sat, Jun 27, 2020 at 10:31 AM Denis Kotov [email protected] wrote: > > Reading PEP554 > > https://www.python.org/dev/peps/pep-0554/#a-disclaimer-about-the-gil > > seems like at the current implementation of subinterpretters there will be > > no separate GIL … > > But I am wondering, why ? > > Each subinterpreter has it own object management and Garbage Collection … > > Why subinterpreters should share one GIL ? > > Is there any technical issues ? > > Sent from Mail https://go.microsoft.com/fwlink/?LinkId=550986 > > for > > Windows 10 > > > > Python-ideas mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > > Message archived at > > https://mail.python.org/archives/list/[email protected]/message/ZC3WVJ... > > Code of Conduct: http://python.org/psf/codeofconduct/ > >
Okay, where is discussions of PEP 554, because I wanted to propose to add `async` API for sub-interpreters in such way using it not required to create new thread, just use event_loop _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/K6PUB3L2VT62HNOEM3HWXFROEJNDXJFO/ Code of Conduct: http://python.org/psf/codeofconduct/
