STINNER Victor <vstin...@redhat.com> added the comment:
> The problem is that loop.close() can "hang" for minutes if there are pending > background jobs or slow DNS resolution requests. Maybe concurrent.futures should be enhanced for that? Or from asyncio, is it possible to poll the executor and emit a warning if some threads take longer than <threshold in esconds>? It would be great if we could display repr() of the slow job in that case. Yury also asked for a timeout, but it's not supported by concurrent.futures yet, and I'm not sure what should be done in case of timeout? Retry? Log a warning? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34037> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
