[issue29564] ResourceWarning tracking is attaching incorrect file:position to unclosed socket
David Ford (FirefighterBlu3)
report at bugs.python.org
Wed Feb 15 06:45:59 EST 2017
David Ford (FirefighterBlu3) added the comment:
@stinner your traceback suggestion was highly useful and much appreciated. i have spent several dozen hours researching ResourceWarnings in the past and tearing my hair out because the emitted warning was very much useless. i couldn't even make educated guesses about the code as socket pairs were used randomly.
i strongly approve of mentioning the tracemalloc / traceback in the warning, and i would also very much encourage saying "this filename:position could be completely wrong" or do away with it all together.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29564>
_______________________________________
More information about the Python-bugs-list
mailing list