Yury Selivanov <yseliva...@gmail.com> added the comment: > It's worse than a resource leak - the same file descriptor number could be > reused for a different file/socket, and then depending on the selector in > use, you could see the data from a completely different connection.
I actually debugged a bug like this in asyncio code once. Took me quite a bit of time to figure it out. > I did see a bug like this years ago (in libcurl), although it's not a common > problem. I'd use the proposed hook if it existed, but it seems like an > intrusive solution to a rare issue. I don't think the proposed solution is too intrusive. If we don't like the "set a callback to intercept all socket.close()" idea, we can change it to: "add socket.add_close_callback() method to the socket object." ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32038> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
