[issue10305] Cleanup up ResourceWarnings in multiprocessing

STINNER Victor added the comment: Oh, I found the issue #25654 which contains more information and even patches. -- superseder: -> test_multiprocessing_spawn ResourceWarning with -Werror ___ Python tracker ___

[issue10305] Cleanup up ResourceWarnings in multiprocessing

STINNER Victor added the comment: Sorry but without any information about the module or function which emits such ResourceWarning, I prefer to close the issue. Anyway, with Python 3.6, it became trivial to identify the root cause of ResourceWarning warinings: https://docs.python.org/dev/whatsn

[issue10305] Cleanup up ResourceWarnings in multiprocessing

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue10305] Cleanup up ResourceWarnings in multiprocessing

Mark Lawrence added the comment: I've looked at managers.py and can't see any evidence that the sockets are ever closed. Please check this out as I can't believe that a technical problem like this could have been around for so long without someone else spotting it during testing, thus meaning

[issue10305] Cleanup up ResourceWarnings in multiprocessing

Ask Solem added the comment: ah, this is something I've seen as well, its part of a bug that I haven't created an issue for yet. -- ___ Python tracker ___ _

[issue10305] Cleanup up ResourceWarnings in multiprocessing

New submission from Brian Curtin : As shown in a debug run of test_multiprocessing, at least two places in managers.py apparently leave open sockets. Lines 786 and 805 are the culprits, both util log lines. -- components: Library (Lib) messages: 120367 nosy: asksol, brian.curtin priori