[issue20567] test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk
Serhiy Storchaka added the comment: Could you try test_ttk_guionly after test_all, test_builtins, test_tcl? If the issue is not reproduced, try to use binary search: divide the tests before test_ttk_guionly on to parts, and run tests with one half, then with other. Repeat until found the culprit. -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20567 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20567] test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk
Serhiy Storchaka added the comment: Threading and subprocess tests also evoke a suspicion. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20567 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20567] test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk
Ned Deily added the comment: $ /usr/local/bin/python3.3 -m test -w -uall test_idle test_ttk_guionly [1/2] test_idle [2/2] test_ttk_guionly can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged All 2 tests OK. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20567 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20567] test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk
Changes by Ned Deily n...@acm.org: -- versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20567 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20567] test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk
Changes by Ned Deily n...@acm.org: -- versions: +Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20567 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20567] test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk
New submission from Ned Deily: Seen with default (3.4.0) framework builds on OS X 10.9 with ActiveTcl 8.5.15.0: ./configure --enable-universalsdk=/ --with-universal-archs=intel --enable-framework=/tmp/t/Library/Frameworks make make install cd /tmp/t /tmp/t/bin/python3.4 -m test -w -uall [...] [343/389/1] test_ttk_guionly can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged can't invoke event command: application has been destroyed while executing event generate $w ThemeChanged (procedure ttk::ThemeChanged line 6) invoked from within ttk::ThemeChanged [344/389/1] test_ttk_textonly [...] When running test_ttk_guionly by itself (or in combination with a few neighboring tests): /tmp/t/bin/python3.4 -m test -w -uall test_ttk_guionly the message is not seen. I had not seen this behavior prior to somewhere in the 3.4.0 development cycle. -- components: Tests, Tkinter messages: 210704 nosy: ned.deily priority: normal severity: normal stage: needs patch status: open title: test_ttk_guionly gets 'can't invoke event command: application has been destroyed' messages from Tk versions: Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20567 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
