[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Erlend E. Aasland added the comment: See also bpo-44229. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Change by Erlend E. Aasland : -- nosy: +erlendaasland ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Change by Daniel King : -- nosy: +Daniel King ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Change by Ronald Oussoren : -- assignee: -> ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Change by Ned Deily : -- components: +asyncio nosy: +asvetlov, yselivanov ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Eamonn Nugent added the comment: Fwiw, this also happens in asyncio. Theoretically, I *think* you could wrap a try-except as a monkey patch. My stack trace is: Fatal write error on socket transport protocol: transport: <_SelectorSocketTransport fd=163 read=polling write=> Traceback (most

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

Ronald Oussoren added the comment: The second link contains an explanation of what's going on, and that this is unexpected behaviour of the macOS kernel. I'm not sure what we could do about this, the blog post explains that this error can happen when send(2) is called

[issue33450] unexpected EPROTOTYPE returned by sendto on MAC OSX

New submission from Richard C : The following exception is raised unexpectedly on macOS versions 10.13, 10.12 & 10.11 at least. It appears to be macOS specific (works okay on Linux). Further information can be found at the following links: