[issue13344] closed sockets don't raise EBADF anymore

2016-06-23 Thread Martin Panter
Martin Panter added the comment: According to strace, Python 3 is calling send(-1, ...): sendto(-1, "x", 1, 0, NULL, 0) = -1 EBADF (Bad file descriptor) A related discrepancy between Python 2 and 3 is how the socket.makefile() objects affect the original socket. In Python 2: >>> f =

[issue13344] closed sockets don't raise EBADF anymore

2013-11-23 Thread Phil Connell
Changes by Phil Connell : -- nosy: +pconnell ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue13344] closed sockets don't raise EBADF anymore

2012-04-20 Thread Colin Marc
Changes by Colin Marc : -- nosy: +colinmarc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13344] closed sockets don't raise EBADF anymore

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

[issue13344] closed sockets don't raise EBADF anymore

2011-11-04 Thread Antoine Pitrou
Antoine Pitrou added the comment: discrepancy, not decrepancy :S (10038 is WSAENOTSOCK, by the way) -- ___ Python tracker ___ ___ Py

[issue13344] closed sockets don't raise EBADF anymore

2011-11-04 Thread Antoine Pitrou
New submission from Antoine Pitrou : This decrepancy between 2.x and 3.x is witnessed under Windows: Python 2.7.1 (r271:86832, Nov 27 2010, 17:19:03) [MSC v.1500 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> sock = socket.cr