[Twisted-Python] twisted listening on UDP port, why?

[Jonathan Vanasco]

On Apr 23, 2016, at 4:52 AM, Phil Mayers wrote:

> Not so. It's down inside the kernel. All applications using the socket API in this way will display this behaviour, regardless of language.
> ....
> 
> As glyph says, this is an inherent feature of the socket API. When you create a socket, it is unbound because you might be about to call bind() yourself.
> 
> If you then use it without binding it, the kernel has to allocate a source port, and in turn an interface, and the only sensible choice absent any instructions from userland is INADDR_ANY.
> 
> This is definitely not Python doing this.

Thanks for the correction!