pipes and queues also keep in mind that because they are pickledobjects transferred this way are effectively copied in the receiving processdirect in-place changes to mutable objectsstate won' be noticed in the sender this makes sense if you remember that this package runs independent processes with their own memory spacesstate cannot be as freely shared as in threadingregardless of which ipc tools you use multiprocessing pipes to demonstrate the ipc tools listed abovethe next three examples implement three flavors of communication between parent and child processes example - uses simple shared pipe object to send and receive data between parent and child processes example - pp \system\processes\multi py ""use multiprocess anonymous pipes to communicate returns connection object representing ends of the pipeobjects are sent on one end and received on the otherthough pipes are bidirectional by default ""import os from multiprocessing import processpipe def sender(pipe)""send object to parent on anonymous pipe ""pipe send(['spam'[ 'eggs']pipe close(def talker(pipe)""send and receive objects on pipe ""pipe send(dict(name='bob'spam= )reply pipe recv(print('talker got:'replyif __name__ ='__main__'(parentendchildendpipe(process(target=senderargs=(childend,)start(print('parent got:'parentend recv()parentend close((parentendchildendpipe(child process(target=talkerargs=(childend,)child start(print('parent got:'parentend recv()parentend send({ for in 'spam'}spawn child with pipe receive from child or auto-closed on gc receieve from child send to child the multiprocessing module