Why sock.bind is always report 10048 error when in a script with multiprocessing

[Chris Angelico]

On Sat, Nov 19, 2011 at 3:11 AM, Junfeng Hu <hujunfeng at gmail.com> wrote:
> Hi Chris.
> The socket only binded once. That's the problem I'm puzzleing, I think it may a bug of multiprocessing in windows, or something I missed.

I don't know how multiprocessing goes about initializing those
subprocesses; I suspect that's where it creates the additional
sockets.

ChrisA