New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-37849: IDLE: fix completion window positioning above line #15267
bpo-37849: IDLE: fix completion window positioning above line #15267
Conversation
Added a mechanism to avoid multiple, recursive invocations of the "<Configure>" event handler, required due to the added .update() call.
New news items go on top, with the fixed length divider line and 2 blank lines above and a blank line and the previous item below. As long as all are backported, all will backport without conflict in either the upper or lower 3-line context. In this case, there was a previous item to be added also. For the first news addition after a final release, which requires a new header at least on that version, the lower context will be different on different versions. So I do the addition on separate PRs (master and manual backports as needed) attached to the current next-version NEWS issue (now bpo 34162 for 3.8). I also use that for corrections and batch additions. |
Thanks @taleinat for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
GH-15282 is a backport of this pull request to the 3.8 branch. |
GH-15283 is a backport of this pull request to the 3.7 branch. |
This also adds a mechanism to avoid multiple, recursive invocations of the "<Configure>" event handler, required due to the added
.update()
call.https://bugs.python.org/issue37849