This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jimbofbx
Recipients Jimbofbx, asksol, dragonfyre13, dsvensson, gsson, jnoller, jodal, pitrou, sbt
Date 2012-04-07.17:46:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

You can just delete my original post. I'll repost an edited version here for reference

original post with paths removed:
This is an issue for me (Python 3.2). I have a custom pool that sends arguments for a function call over a pipe. I cannot send another pipe as an argument. 

Tim's workaround also does not work for me (win xp 32bit and 64bit)

From what I can tell, you can only send a connection as a direct argument to a function call. This limits what I can do because I cannot introduce new pipes to a worker process after it is instantiated.

Using this code:

def main():
    from multiprocessing import Pipe, reduction
    i, o = Pipe()
    reduced = reduction.reduce_connection(i)
    newi = reduced[0](*reduced[1])

if __name__ == "__main__":

This is my output:

<read-write PipeConnection, handle 1760>
(<function rebuild_connection at 0x00FD4C00>, (('\\\\.\\pipe\\pyc-3156-1-q5wwnr', 1756, False), True, True))
<read-write Connection, handle 1720>
>>> newi.send("hi")
IOError: [Errno 10038] An operation was attempted on something that is not a socket

As you can see, the handle changes
Date User Action Args
2012-04-07 17:46:11Jimbofbxsetrecipients: + Jimbofbx, pitrou, jnoller, gsson, dsvensson, asksol, jodal, dragonfyre13, sbt
2012-04-07 17:46:11Jimbofbxsetmessageid: <>
2012-04-07 17:46:10Jimbofbxlinkissue4892 messages
2012-04-07 17:46:10Jimbofbxcreate