[issue15707] PEP 3121, 384 Refactoring applied to signal module

Change by STINNER Victor : -- resolution: fixed -> duplicate superseder: -> _signal module leak: test_interpreters leaked [1424, 1422, 1424] references ___ Python tracker ___

[issue15707] PEP 3121, 384 Refactoring applied to signal module

STINNER Victor added the comment: The _signal extension module has been ported to the new multi-phase initialization API (PEP 489). See bpo-4 "Convert a few stdlib extensions to the limited C API". -- nosy: +vstinner resolution: -> fixed stage: -> resolved status: open -> close

[issue15707] PEP 3121, 384 Refactoring applied to signal module

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue15707] PEP 3121, 384 Refactoring applied to signal module

Mark Lawrence added the comment: PEP 384 is listed as finished while 3121 is accepted so what if anything needs to be done here? I've checked https://docs.python.org/devguide/experts.html and nobody is listed against the signal module. The patch is C code which I don't have the knowledge to

[issue15707] PEP 3121, 384 Refactoring applied to signal module

Changes by Robin Schreiber : -- keywords: +pep3121 -patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue15707] PEP 3121, 384 Refactoring applied to signal module

New submission from Robin Schreiber: Changes proposed in PEP3121 and PEP384 have now been applied to the signal module! -- components: Extension Modules files: signal_pep3121-384_v0.patch keywords: patch messages: 168415 nosy: Robin.Schreiber priority: normal severity: normal status: op