Phill added the comment:
Rather than listening on a socket, listening on a named pipe
eg:
address = (r'\\.\pipe\Test', 'AF_PIPE')
listener = Listener(*address)
conn = listener.accept()
It doesnt raise an exception when i run the script again a second time.
Like I said, I
Phill added the comment:
I have commented out the line:
self._socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
In lib/multiprocessing/connection.py
as a test and it works fine, the problem still persists for named pipes (im not
sure if thats how named pipes are supposed to behave
Phill added the comment:
Normally I would be happy to but my combined python experience is about 30
minutes so I am probably not the man
--
___
Python tracker
<http://bugs.python.org/issue8
Phill added the comment:
@neologix: nah its fine, if you guys are gonna re open this one I wont worry
about opening a new bug.
If the above gets solved on windows my problem will just go away, thanks
--
versions: +Python 2.6 -Python 2.7, Python 3.2, Python 3.3
Phill added the comment:
Im not sure whether to open a new bug report for my issue or just leave it here.
--
___
Python tracker
<http://bugs.python.org/issue8
Phill added the comment:
I have run into the same problem with python 3.2 & 2.7 on windows 7 with the
Listener object. It opens the same port twice for some wierd reason
I have tried the example in this bug report and i am getting the same behavoir
as the original poster
--
