This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author akineko
Recipients akineko, jahakala
Date 2009-04-03.21:58:36
SpamBayes Score 4.0076814e-10
Marked as misclassified No
Message-id <1238795918.64.0.283473579067.issue5527@psf.upfronthosting.co.za>
In-reply-to
Content
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-
History
Date User Action Args
2009-04-03 21:58:38akinekosetrecipients: + akineko, jahakala
2009-04-03 21:58:38akinekosetmessageid: <1238795918.64.0.283473579067.issue5527@psf.upfronthosting.co.za>
2009-04-03 21:58:37akinekolinkissue5527 messages
2009-04-03 21:58:36akinekocreate