Repository navigation
Use lambdas to prevent gc'ing and deduplication of widget callbacks. - #18923
Merged
Merged
Conversation
This makes the behavior of widget callbacks more consistent with the old behavior (of using strong refs), and also more consistent with other widgets which don't rely on CallbackRegistry at all, such as SpanSelector and Lasso.
tacaswell
approved these changes
Nov 10, 2020
QuLogic
approved these changes
Nov 11, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This makes the behavior of widget callbacks more consistent with the old
behavior (of using strong refs), and also more consistent with other
widgets which don't rely on CallbackRegistry at all, such as
SpanSelector and Lasso.
See #18226 (comment).
PR Summary
PR Checklist
pytestpasses).flake8on changed files to check).flake8-docstringsand runflake8 --docstring-convention=all).doc/users/next_whats_new/(follow instructions in README.rst there).doc/api/next_api_changes/(follow instructions in README.rst there).