Message230444
| Author |
ned.deily |
| Recipients |
ned.deily, serhiy.storchaka, terry.reedy |
| Date |
2014年11月01日.09:57:37 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1414835858.31.0.373937885209.issue22770@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Ah, Issue18604! Thanks for the reminder (and for the patch), Serhly! Focusing on these more recent occurrences of segfaults, I hadn't been thinking about those earlier ones. Now, after digging into Tk and identifying the problem there, it's clear that those earlier segfaults reported in Issue18604 were a result of the same Tk bug, just caused slightly differently from the tkinter tests. The #18604 changes also caused a Tcl interpreter instance to be created and destroyed without actually causing Tk to do enough to cause the "open application" Apple event to be fired and received. _is_gui_available is the right place and adding the additional Tk activity there does it at the right time. And it appears that root.update() is sufficient, as you suggested. I want to do some additional testing but, assuming no problems are found, I'll plan to apply the simplified patch. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年11月01日 09:57:38 | ned.deily | set | recipients:
+ ned.deily, terry.reedy, serhiy.storchaka |
| 2014年11月01日 09:57:38 | ned.deily | set | messageid: <1414835858.31.0.373937885209.issue22770@psf.upfronthosting.co.za> |
| 2014年11月01日 09:57:38 | ned.deily | link | issue22770 messages |
| 2014年11月01日 09:57:37 | ned.deily | create |
|