[issue4929] smptlib.py can raise socket.error

Kristján Valur Jónsson added the comment: Note, this has been ported to py3k in http://svn.python.org/view? view=rev&rev=68736 ___ Python tracker ___ _

[issue4929] smptlib.py can raise socket.error

Kristján Valur Jónsson added the comment: Submitted as r68618 -- resolution: -> accepted status: open -> closed ___ Python tracker ___ __

[issue4929] smptlib.py can raise socket.error

Giampaolo Rodola' added the comment: IMHO I wouldn't test such case. Behaviors between different platform are unpredictable. ___ Python tracker ___ ___

[issue4929] smptlib.py can raise socket.error

Gabriel Genellina added the comment: On Windows, if you exit a process abnormally (using e.g. os._exit() in Python) while it still has open connections, the other side receives a WSAECONNRESET (error 10054). So, you could write a test case using a dumb server (running as another process) wit

[issue4929] smptlib.py can raise socket.error

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue4929] smptlib.py can raise socket.error

Kristján Valur Jónsson added the comment: If you can offer a suggestion as to how to reliably trigger a WSAECONNRESET error on windows (or its equivalent on unix) I'll be happy to do that. ___ Python tracker _

[issue4929] smptlib.py can raise socket.error

STINNER Victor added the comment: Your patch looks fine but it would be much better with a test in Lib/test/test_smtp.py ;-) -- nosy: +haypo ___ Python tracker ___ _

[issue4929] smptlib.py can raise socket.error

New submission from Kristján Valur Jónsson : the SMPT.getreply() method doesn't check for socket.error when doing its readline() call. We now check for connection reset and others that can occur here and properly close. This is to comply with the documentation that doesn't specify socket.err