New submission from Stefan Krah:
unittest produces the following resource warnings:
$ ./python -m test -uall test_asyncio
[1/1] test_asyncio
/home/stefan/hg/master/Lib/unittest/case.py:571: ResourceWarning: unclosed
<socket.socket fd=7, family=2, type=1, proto=0, laddr=('127.0.0.1', 49177)>
testMethod()
/home/stefan/hg/master/Lib/unittest/case.py:571: ResourceWarning: unclosed
<socket.socket fd=7, family=2, type=1, proto=0, laddr=('127.0.0.1', 56385)>
testMethod()
/home/stefan/hg/master/Lib/unittest/case.py:571: ResourceWarning: unclosed
<socket.socket fd=7, family=2, type=1, proto=0, laddr=('127.0.0.1', 56244)>
testMethod()
[...]
It seems to happen whenever run_test_server() from asyncio/test_utils.py is
used.
----------
components: Tests
messages: 200417
nosy: skrah
priority: normal
severity: normal
status: open
title: test_asyncio: unclosed sockets
versions: Python 3.4
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19297>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
