Right way of keeping module from destruction#11715
Right way of keeping module from destruction#11715vinnik-dmitry07 wants to merge 4 commits intoaio-libs:masterfrom
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #11715 +/- ##
=======================================
Coverage 98.73% 98.73%
=======================================
Files 127 127
Lines 43558 43558
Branches 2320 2320
=======================================
+ Hits 43007 43008 +1
Misses 390 390
+ Partials 161 160 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
CodSpeed Performance ReportMerging #11715 will not alter performanceComparing Summary
|
What exception? (your reproducer is not complete, and doesn't seem to reproduce on my machine) |
|
I had to look up why this was used in the first place. For anyone else, relevant part of the docs:
|
|
@vinnik-dmitry07 could you write a test for this at least? |

To reproduce:
# Old example, look below for a new oneWhat do these changes do?
Fixes Exception ignored in sys.unraisablehook:
You should store the function not the module.
Are there changes in behavior for the user?
No.
Is it a substantial burden for the maintainers to support this?
No.