| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Since I'm waiting for Kirill's review, I'll also run the build bots! |
Sorry, something went wrong.
|
There is no ref leak: $ ./python -m test test_curses -u all -R 3:3 (...) Result: SUCCESS |
Sorry, something went wrong.
We also remove the use of a the `file` role since we incorrectly used it :')
There was a problem hiding this comment.
LGTM. 🚀
Sorry, something went wrong.
|
Merged, thanks. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
I think this should do the job. I observed that there are more reference leaks but I think it's normal since I don't know of any way to actually clear the heap type in a single-phase initialization module.
The only way I can think of clearing it is to add some finalization callback at interpreter's shutdown but I think this is not a good idea because we'll likely transform the module into a multi-phase initialization module in the next PR.
However, I'd like to have some additional eyes (cc @encukou @Eclips4) to indeed check that the reference leaks that I introduced are inevitable and not due to how I defined the heap type.
📚 Documentation preview 📚: https://cpython-previews--124934.org.readthedocs.build/