On Wed, Jun 10, 2020 at 5:37 AM Mark Shannon <m...@hotpy.org> wrote: > By sharing an address space the separation is maintained by trust and hoping that third party modules don't have too many bugs.
By definition, the use of any third-party module (or even the standard library itself) is by trust and the hope that they don't have too many bugs. Sure, this creates a potential new class of bugs, for those who use it, while also offering the chance to find and fix old bugs like Victor found. Mostly, though, it exposes lots of bad practices that people could mostly get away with as long as the assumption was that everything would always be single-threaded, single-process, and the entire software industry is moving away from those assumptions, so it's only logical that Python takes advantage of that shift instead of becoming another legacy language. In the meantime, modules can explicitly label themselves as single-interpreter only, requiring multiprocessing instead of threading or embedding to work correctly. Modules were more than happy to label themselves as 2.x only for a decade -Em
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/JKELVIZHMZRS4VPBNJFWSP5POACQ4ODU/ Code of Conduct: http://python.org/psf/codeofconduct/
