Aki <akin...@users.sourceforge.net> added the comment: Hello Jani Hakala,
Thank you very much for working on the case I created. And, sorry for not getting back to you. I have confirmed observation that the problem is fixed under Linux if Tkinter is imported after fork(). However, this remains a problem for me and most other Tkinter programmers. It is fairy common to import Tkinter using from Tkinter Import *. This is because otherwise all Tk constants need to be prefixed with Tkinter. That is very painful and I don't see such coding except small examples. If I import Tkinter module after fork(), I cannot use from Tkinter *. Therefore this forces programmers to use Tkinter. prefix for every Tk constants. Is there any way to figure out the cause of this problem? Or, is there any way to do "from Tkinter import *" after fork()? Thank you for your help. Aki- ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5527> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
