Ronald Oussoren <ronaldousso...@mac.com> added the comment: As I mentioned in msg314304 this is almost certainly expected behavior on macOS because Apple’s GUI frameworks are not fork()-safe. There is nothing we can do about this other than changing the default spawn mechanism for multiprocessing on macOS.
-- On the road, hence brief. Op 14 jul. 2018 om 19:30 heeft Terry J. Reedy <rep...@bugs.python.org> het volgende geschreven: > > Terry J. Reedy <tjre...@udel.edu> added the comment: > > On MacOS, 3.7.0 is compiled for and the installer loads tcl/tk 8.6.8. The > same is true for the 3.6.6 64-bit installer. Do tkinter and multiprocessing > work together better with these installations? > > I want to consider using multiprocessing and pipes instead subprocess and > socket for IDLE's user-code execution process, started from and communicating > with the initial tkinter gui process. idlelib.run, which runs in the > execution process to communicae with the gui process and supervise running > user code, imports tkinter. Besides which, users have to be able to import > tkinter in their programs. > > ---------- > nosy: +pitrou > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue33111> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33111> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
