From: Ned D. <na...@ac...> - 2011-01-22 21:25:21
|
See http://bugs.python.org/issue10973 and https://sourceforge.net/tracker/index.php?func=detail&aid=2907388&group_i d=12997&atid=112997 As I commented on the SF tracker: "This is a really nasty bug and, with the release of Cocoa Tk backports to Tk 8.5, as in the Tcl/Tk 8.5.7 shipped by Apple in Mac OS X 10.6 and recent ActiveState Tcl/Tk 8.5.9, it is impacting more applications and users. In OS X 10.6, the Apple-supplied Python Tkinter modules and, thus, IDLE are susceptible to this crash: /usr/bin/idle2.6 and, with the US Extended input method, type Option-u (umlaut combiner) or Option-n (tilde combiner), for instance. For the Python Software Foundation (python.org) Python installers for OS X, we were intending to support 64-bit Python with a recommendation to use the ActiveState 8.5.9 Tcl/Tk (since the Apple-supplied one has so many other problems with Tkinter and IDLE) but this easy crasher seems to be a show stopper for that (http://bugs.python.org/issue10973). I see that postfix combining characters (like Shift-Option-u) work without crashing. It also appears that the system Character Viewer input does not work at all. Any prognosis on a fix for this problem?" I haven't been a regular follower of this list and, with a quick search of the list archives, I didn't find any previous discussion of this here. Can anyone point me to such or, better, give an update on if and when a fix is likely to appear in either Apple's or ActiveState's Cocoa 8.5? Since the Python 3.2 release is less than a month away, we might have to pull Cocoa Tk support which would be unfortunate. Thanks! --Ned -- Ned Deily, na...@ac... |
From: Torsten B. <re...@ma...> - 2011-01-22 23:38:49
|
Hi, I do not think that an update is coming quickly for Apple's Cocoa Tk version. It takes quite a long time from an initial submission of Tk to the moment it is shipped. But Daniel Steffen can say more about this. What I did until now, and this may not be an option for you, is to patch the sources just enough to avoid the crash. The accent is just suppressed and an un-accented character comes out instead. It just takes a simple additional 'if' statement in tkMacOSXKeyEvent.c: [... lines 1-144 in current cvs version ...] if (type == NSKeyUp || repeat) { xEvent.xany.type = KeyRelease; } else { xEvent.xany.type = KeyPress; } // prevent bug here -> composite characters if ([characters length] > 0) { xEvent.xkey.keycode = (keyCode << 16) | (UInt16) [characters characterAtIndex:0]; if (![characters getCString:xEvent.xkey.trans_chars maxLength:XMaxTransChars encoding:NSUTF8StringEncoding]) { TkMacOSXDbgMsg("characters too long"); return theEvent; } } len = [charactersIgnoringModifiers length]; [... lines 161-356 in current cvs version ...] Of course, a correct solution would be best, but my skills are not good enough for this. I tried several things, looked for similar code on the net, but without success. So, we will have to wait until someone takes care of this issue and I suspect that Daniel is just too busy right now. Torsten > See http://bugs.python.org/issue10973 > > and > > https://sourceforge.net/tracker/index.php?func=detail&aid=2907388&group_i > d=12997&atid=112997 > > As I commented on the SF tracker: > > "This is a really nasty bug and, with the release of Cocoa Tk > backports to Tk 8.5, as in the Tcl/Tk 8.5.7 shipped by Apple in Mac OS > X 10.6 and recent ActiveState Tcl/Tk 8.5.9, it is impacting more > applications and users. In OS X 10.6, the Apple-supplied Python > Tkinter modules and, thus, IDLE are susceptible to this crash: > /usr/bin/idle2.6 and, with the US Extended input method, type Option-u > (umlaut combiner) or Option-n (tilde combiner), for instance. For the > Python Software Foundation (python.org) Python installers for OS X, we > were intending to support 64-bit Python with a recommendation to use > the ActiveState 8.5.9 Tcl/Tk (since the Apple-supplied one has so many > other problems with Tkinter and IDLE) but this easy crasher seems to > be a show stopper for that (http://bugs.python.org/issue10973). I see > that postfix combining characters (like Shift-Option-u) work without > crashing. It also appears that the system Character Viewer input does > not work at all. > > Any prognosis on a fix for this problem?" > > I haven't been a regular follower of this list and, with a quick search > of the list archives, I didn't find any previous discussion of this > here. Can anyone point me to such or, better, give an update on if and > when a fix is likely to appear in either Apple's or ActiveState's Cocoa > 8.5? Since the Python 3.2 release is less than a month away, we might > have to pull Cocoa Tk support which would be unfortunate. > > Thanks! > --Ned > > -- > Ned Deily, > na...@ac... > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Tcl-mac mailing list > tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac |
From: Kevin W. <kw...@co...> - 2011-01-23 01:55:39
|
Torsten, Could you please put your code together into a full-fledged patch and either send it here to the Tcl-Mac list or to the SF tracker, if you haven't already? I'd be glad to review it and apply it as a short-term workaround for this bug. Ned, Fixing this bug in CVS HEAD is not likely to address your concerns in the near term. Apple does not update its version of Tcl/Tk except at new releases of the OS, not at point releases. (IOW don't look for a new version until Lion is out.) Daniel Steffen is pretty good about merging updates from CVS HEAD into his 8.5 backport of Tk-Cocoa, but that likely won't happen until the next point release of Tk (8.5.10, if I'm correct). ActiveState is basing its release of Tcl/Tk on the Cocoa version even in 8.5.x, so the bugfix should show up there after the next point release of 8.5. Thanks, Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com |
From: Torsten B. <re...@ma...> - 2011-01-23 11:44:00
|
Hi, I just uploaded a pathced version of tkMacOSXKeyEvent.c to the bug at SF. Torsten > > Could you please put your code together into a full-fledged patch and > either send it here to the Tcl-Mac list or to the SF tracker, if you > haven't already? I'd be glad to review it and apply it as a short-term > workaround for this bug. > > Ned, > > Fixing this bug in CVS HEAD is not likely to address your concerns in > the near term. Apple does not update its version of Tcl/Tk except at new > releases of the OS, not at point releases. (IOW don't look for a new > version until Lion is out.) Daniel Steffen is pretty good about merging > updates from CVS HEAD into his 8.5 backport of Tk-Cocoa, but that likely > won't happen until the next point release of Tk (8.5.10, if I'm > correct). ActiveState is basing its release of Tcl/Tk on the Cocoa > version even in 8.5.x, so the bugfix should show up there after the next > point release of 8.5. > > Thanks, > Kevin > > -- > Kevin Walzer > Code by Kevin > http://www.codebykevin.com > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Tcl-mac mailing list > tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac |
From: Ned D. <na...@ac...> - 2011-01-23 18:57:22
|
In article <D2C...@ma...>, Torsten Berg <re...@ma...> wrote: > I just uploaded a pathced version of tkMacOSXKeyEvent.c to the bug at SF. Thanks, Torsten. And, thanks, Kevin, for looking into this. I don't really want to get us into the business of building and shipping Tk with python.org installers but, if an official patch prevents this nasty crash and doesn't cause any other regressions, it might be worth it. -- Ned Deily, na...@ac... |
From: Kevin W. <kw...@co...> - 2011-01-24 15:26:39
|
On 1/23/11 1:56 PM, Ned Deily wrote: > In article<D2C...@ma...>, > Torsten Berg<re...@ma...> wrote: >> I just uploaded a pathced version of tkMacOSXKeyEvent.c to the bug at SF. > > Thanks, Torsten. And, thanks, Kevin, for looking into this. I don't > really want to get us into the business of building and shipping Tk with > python.org installers but, if an official patch prevents this nasty > crash and doesn't cause any other regressions, it might be worth it. > I've committed Torsten's patch--thanks, Torsten. This works around the issue by avoiding the crash, but I'm still not able to input some composite characters (option-u, for instance): the keyboard input is ignored. (Shift-option-u does work.) Composite characters and Unicode are surprisingly difficult to manage in Cocoa; I've spent a number of hours investigating this and was not able to find any solution to the question. Torsten's patch is the only workable solution for the moment. --Kevin -- Kevin Walzer Code by Kevin http://www.codebykevin.com |
From: Damon C. <da...@tc...> - 2011-01-24 16:30:08
|
You might ping Andreas Kupries (and...@ac...) over at ActiveState. He handles the releases over there. If you guys already recommend people install ActiveTcl (and you should over the default OS X install), you might be able to convince them that this bug is severe enough to do a small point release of ActiveTcl to fix it. Then you would just recommend at least that version for Python. It's not ideal since it's not in any "official" release from the Core Team, but for many people, ActiveTcl is as official as it gets. And they are on their own release schedule as they see fit. I'm pretty sure he might already watch this list, and if not, I know Jeff Hobbs does. He never responds to anything though. 0-] D On Jan 23, 2011, at 12:56 PM, Ned Deily wrote: > In article <D2C...@ma...>, > Torsten Berg <re...@ma...> wrote: >> I just uploaded a pathced version of tkMacOSXKeyEvent.c to the bug at SF. > > Thanks, Torsten. And, thanks, Kevin, for looking into this. I don't > really want to get us into the business of building and shipping Tk with > python.org installers but, if an official patch prevents this nasty > crash and doesn't cause any other regressions, it might be worth it. > > -- > Ned Deily, > na...@ac... > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > Tcl-mac mailing list > tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac |
From: Jeff H. <je...@ac...> - 2011-01-24 17:58:44
|
On 23/01/2011 10:56 AM, Ned Deily wrote: > In article<D2C...@ma...>, > Torsten Berg<re...@ma...> wrote: >> I just uploaded a pathced version of tkMacOSXKeyEvent.c to the bug at SF. > > Thanks, Torsten. And, thanks, Kevin, for looking into this. I don't > really want to get us into the business of building and shipping Tk with > python.org installers but, if an official patch prevents this nasty > crash and doesn't cause any other regressions, it might be worth it. I'll make sure that we have an ActiveTcl release updated with this patch prior to Feb 12. Note that we are using the 8.5-decarbon branch created by Daniel Steffen, which is not the "official" 8.5 source branch (that one still has the carbon sources). Thus, no need for an official 8.5 release related to this, and I suspect most people aren't using Tkinter and 8.6 at this time. Jeff |
From: Ned D. <na...@ac...> - 2011-01-24 20:19:18
|
In article <4D3...@ac...>, Jeff Hobbs <je...@ac...> wrote: > On 23/01/2011 10:56 AM, Ned Deily wrote: > > In > > article<D2CFDFB0-A7CB-4468-8660-BF346BB49120-dKc1CtW5WJqELgA04lAiVw@public.g > > mane.org>, > > Torsten Berg<re...@ma...> wrote: > >> I just uploaded a pathced version of tkMacOSXKeyEvent.c to the bug at SF. > > > > Thanks, Torsten. And, thanks, Kevin, for looking into this. I don't > > really want to get us into the business of building and shipping Tk with > > python.org installers but, if an official patch prevents this nasty > > crash and doesn't cause any other regressions, it might be worth it. > > I'll make sure that we have an ActiveTcl release updated with this patch > prior to Feb 12. Note that we are using the 8.5-decarbon branch created > by Daniel Steffen, which is not the "official" 8.5 source branch (that > one still has the carbon sources). Thus, no need for an official 8.5 > release related to this, and I suspect most people aren't using Tkinter > and 8.6 at this time. Jeff, That's great! Thanks so much to you and Kevin and Torsten. If there's anything we can do to test it, let me know. While I have your combined attention, there's one other non-critical issue with Cocoa Tk 8.5 that could perhaps be addressed, that is the "setCanCycle: is deprecated" running on 10.6. I'll start a new thread about that. -- Ned Deily, na...@ac... |