Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Dec 4, 2017

When tk event handling is driven by IDLE's run loop, a confusing
and distracting queue.EMPTY traceback context is no longer added
to tk event exception tracebacks. The traceback is now the same
as when event handling is driven by user code. Patch based on
a suggestion by Serhiy Storchaka.
(cherry picked from commit 1e2fcac)

https://bugs.python.org/issue32207

)

When tk event handling is driven by IDLE's run loop, a confusing
and distracting queue.EMPTY traceback context is no longer added
to tk event exception tracebacks.  The traceback is now the same
as when event handling is driven by user code.  Patch based on
a suggestion by Serhiy Storchaka.
(cherry picked from commit 1e2fcac)
@miss-islington
Copy link
Contributor Author

@terryjreedy: Backport status check is done, and it's a success ✅ .

@terryjreedy terryjreedy merged commit 9da33c8 into python:3.6 Dec 4, 2017
@miss-islington
Copy link
Contributor Author

Thanks, @terryjreedy!

@miss-islington miss-islington deleted the backport-1e2fcac-3.6 branch December 4, 2017 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants