| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I think it is worth the risk to backport memory-leak fixes. |
Sorry, something went wrong.
|
The flake8 is understood and fixed else where already. |
Sorry, something went wrong.
|
This could lead to user breakage since things that were once immortal are now possibly short lived, just like in the original issue. |
Sorry, something went wrong.
|
Maybe that was a hasty comment. They should live until someone calls destroy on canvas.get_tk_widget() or its parent, which should be reasonably predictable. |
Sorry, something went wrong.
|
Okay, having convinced myself that these changes work I think it seems fine. @richardsheridan are you still thinking that things may be too short lived, or was that last comment pretty convinced it is okay? |
Sorry, something went wrong.
|
I'm satisfied that those binds won't be released too early from any practical user perspective. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
Fixes #24820
May be worth checking if the memory leak tests can be tightened.
PR Checklist
Documentation and Tests
Release Notes