Richard Oudkerk added the comment: > So hopefully the bug should disappear entirely in future releases of tcl, > but for now you can work around it by building tcl without threads, > calling exec in between the fork and any use of tkinter in the child > process, or not importing tkinter until after the fork.
In 3.4 you can do this by using multiprocessing.set_start_method('spawn') ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5527> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com