[issue13888] test_builtin failure when run after test_tk

STINNER Victor added the comment: I cannot reproduce this issue on the Python main branch on Fedora 35 with Tk 8.6.10 and libX11 1.7.3.1. I close the issue, please reopen it if you can still reproduce it. One year ago, Serhiy wrote that the issue was still reproducible on Linux but he didn'

[issue13888] test_builtin failure when run after test_tk

Serhiy Storchaka added the comment: It is still reproducible on Linux. I do not get a crash, just test failure and some strange output. == FAIL: test_input_tty_non_ascii (test.test_builtin.PtyTests) ---

[issue13888] test_builtin failure when run after test_tk

Terry J. Reedy added the comment: tcl/tk 8.5, likely used in 2012 test, was by default compiled without thread support. 8.6, used now for sure on psf Windows and Macs installs and I believe on most *nixes, the default is *with* thread support. Given the comments, this might affect results.

[issue13888] test_builtin failure when run after test_tk

Irit Katriel added the comment: I couldn't reproduce this on a macOS (3.10). Is it still an issue? -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___ ___

[issue13888] test_builtin failure when run after test_tk

Serhiy Storchaka added the comment: This is due PyOS_InputHook. After commenting out EnableEventHook() tests are passed. -- nosy: +serhiy.storchaka ___ Python tracker ___ __

[issue13888] test_builtin failure when run after test_tk

Changes by STINNER Victor : -- components: +Tests, Tkinter -XML ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13888] test_builtin failure when run after test_tk

STINNER Victor added the comment: "python: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed." I get a similar XCB assertion error: "xcb_io.c:221: poll_for_event: Assertion `(((long) (event_sequence) - (long) (dpy->request)) <= 0)' failed." The problem

[issue13888] test_builtin failure when run after test_tk

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13888] test_builtin failure when run after test_tk

Terry J. Reedy added the comment: This is not a problem on Windows because the failing tests are skipped. test_input_tty (test.test_builtin.BuiltinTest) ... skipped 'the pty and signal modules must be available' test_input_tty_non_ascii (test.test_builtin.BuiltinTest) ... skipped 'the pty and

[issue13888] test_builtin failure when run after test_tk

New submission from Nadeem Vawda : While investigating issue 13886, I found that test_builtin will fail when run after test_tk: $ ./python -Wd -E -bb -m test -vuall test_tk test_builtin == CPython 3.3.0a0 (default:52f68c95e025, Jan 26 2012, 19:05:09) [GCC 4.6.1] == Linux-3.0.0-15-g