[issue5503] multiprocessing/connection.py wrong pipe name under win32

2009-06-29 Thread Jesse Noller
Jesse Noller added the comment: Closing; without the exception/more details, and with multiprocessing working on WIN32 I don't have anything to go on. -- resolution: -> wont fix status: pending -> closed ___ Python tracker

[issue5503] multiprocessing/connection.py wrong pipe name under win32

2009-03-31 Thread Jesse Noller
Jesse Noller added the comment: I need to know what the exception/error is, given multiprocessing is working fine on WIN32. Setting status to pending - without a test case that shows the issue or more information, I can not move forward with this. -- status: open -> pending

[issue5503] multiprocessing/connection.py wrong pipe name under win32

2009-03-18 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- assignee: -> jnoller nosy: +jnoller priority: -> normal type: -> behavior versions: +Python 2.7, Python 3.0, Python 3.1 ___ Python tracker ___ __

[issue5503] multiprocessing/connection.py wrong pipe name under win32

2009-03-17 Thread jq
New submission from jq : def arbitrary_address(family): elif family == 'AF_PIPE': return tempfile.mktemp(prefix=r'\\.\pipe\pyc-%d-%d-' % (os.getpid(), _mmap_counter.next())) #works after removed tempfile.mktemp return r'\\.\pipe\pyc-%d-%d-' % (o