[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

Martin v. Löwis added the comment: Thanks for the advice. I managed to fix this (for me) in r79907; I had to force focus before every single event :-( -- keywords: +buildbot resolution: -> fixed stage: -> committed/rejected status: open -> closed

[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

Changes by Guilherme Polo : Removed file: http://bugs.python.org/file16818/p1.diff ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

Guilherme Polo added the comment: When I run that alone I get the same effect, maybe there is something else contributing to the previous result I saw. focus_force did solve when testing it alone, and I think it is ok to use focus_force when testing at least. Here is the sample I tried: import

[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

Martin v. Löwis added the comment: > Could it be caused because the notebook is not focused at the correct > time ? Here in OSX (finally I have one of these) I had to add > self.nb.focus() before that event_generate. No, that doesn't help. The event still gets lost. In particular, running ttk:

[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

Guilherme Polo added the comment: > Martin v. Löwis added the comment: > > I can reproduce the problem. The root cause is that the "event generate .nb > " simply does not have any effect - neither through Python, nor > through directly wish. Nor do any of the other keys that supposedly cycle

[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

Martin v. Löwis added the comment: I can reproduce the problem. The root cause is that the "event generate .nb " simply does not have any effect - neither through Python, nor through directly wish. Nor do any of the other keys that supposedly cycle through the notebook, when send through "eve

[issue8204] test_ttk_guionly assertion error on 3.x linux 64-bit

New submission from Sridhar Ratnakumar : This happens on 3.1.2 Linux 64-bit. test test_ttk_guionly failed -- Traceback (most recent call last): File "/home/apy/rrun/tmp/autotest/apy/lib/python3.1/tkinter/test/test_ttk/test_widgets.py", line 708, in test_traversal self.assertEqual(self.nb