|
From: Emiliano <emi...@gm...> - 2025-10-22 01:13:11
|
Hi Kevin Se comments below > I do not intend to have the test suite run with a screen reader active - > there is too much overhead with accessibility that may cause conflicts > and failures with the test suite. In fact, some of my recent commits > have been intended to ensure that the accessibility commands do not leak > into the test suite when the screen reader is inactive. Is the above > hang occurring with, or without, a screen reader? The hang occurs without the screen reader active. > I've added this change because it seems to be make sense, but I am not > changing functionality in child interpreters. The problem is that TkAccessibility_Init is run on every child interpreter that loads Tk, but the TkAccessibilityObject hash table should be initialized just once. > I've added a cleanup handler for the global TkAccessibilityObject for > app exit. This is desirable, yes. But the cleanup I had in mind is when widgets are destroyed; if not cleaned up, the entries will still be there even when they are not needed anymore. See attached patch for a simple solution. Regards. -- Emiliano |