[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Changes by Antoine Pitrou : -- nosy: +gpolo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Ronald Oussoren added the comment: In python 2.x 'MacOS.WMAvailable()' returns True if the windowserver is available. The whole MacOS extension is gone in 3.x, although it should be easy enough to reimplement WMAvailable() using ctypes. -- ___ Py

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

R. David Murray added the comment: I just ran into this while trying to run the test suite with -uall while sshed into an OSX machine and running a non-framework build. This makes it kind of hard to run the full test suite. Is there some way to detect that we don't have access to the window

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Ronald Oussoren added the comment: Tk has a different tracker than tcl itself, the upstream issue is now -- ___ Python tracker

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Ronald Oussoren added the comment: Something I forgot to mention: the patch introduces "_tkinter.m" to enable compiling the _tkinter extension as Objective-C code. The compiler also supports passing "-x objective-c" to compile _tkinter.c in Objective-C mode, but this flag must be specified e

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Ronald Oussoren added the comment: The attached patch is a first start at working around the crash. With this patch I can use Tk without a crash: >>> import Tkinter >>> Tkinter.Tk() Sun May 16 12:11:08 Rivendell.local python.exe[55984] : kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint()

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Ronald Oussoren added the comment: BTW. Another way of testing, assuming you have two accounts: use 'su - otheraccount' to get a shell session as another user then try to start tk using: import Tkinter root = Tkinter.Tk() This will currently crash the interpreter due to an uncaught Objective-

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Ronald Oussoren added the comment: I've filed an issue for this in the Tcl/Tk tracker: (Assuming that this is the canonical tracker for the Tcl/Tk project, it was the first hit in google for 'tk bug tracker'

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Bill Janssen added the comment: It's fairly easy to create a restricted process tree for testing. ssh into a Mac which has no one logged into the console, from another machine, and use that connection to launch an xterm or Xemacs window to the other machine. Then log out of the ssh session.

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

Bill Janssen added the comment: [More info from Ronald Oussoren] This is a bug in Tk: >>> root = Tkinter.Tk() Thu May 13 20:45:13 Rivendell.local python[84887] : kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged. _RegisterApplication(), FAILED TO esta

[issue8716] test_tk fails on OS X if run from buildbot slave daemon -- crashes Python

New submission from Bill Janssen : test_tk fails on OS X if test is run from a daemon process without the privilege to access the window server, say a buildbot slave without anyone logged in to the console. The Tk support needs to check whether it has access rights to the window server before