[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Changes by Richard Oudkerk : -- resolution: -> works for me stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Richard Oudkerk added the comment: > I have repaired my class so that it pickles properly, but that does not > resolve the issue that if you send a non-picklable object through a pipe, > it should raise an error, rather than hang. What do you mean by hang? Do you mean that send() succeeds an

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Ian Bell added the comment: I have repaired my class so that it pickles properly, but that does not resolve the issue that if you send a non-picklable object through a pipe, it should raise an error, rather than hang. -- ___ Python tracker

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Senthil Kumaran added the comment: On Sun, Jul 1, 2012 at 1:16 AM, Richard Oudkerk wrote: > Then I doubt this is a bug in Python. I guess, you meant, this is NOT a bug in Python. -- nosy: +orsenthil ___ Python tracker

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Richard Oudkerk added the comment: Then I doubt this is a bug in Python. If your class does not override __reduce__, __reduce_ex__ or __getstate__/__setstate__, then it is probably one of the attributes of your instance which is causing the problem. You could try to find out which one by tr

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Ian Bell added the comment: I had issues with a class that I wrote myself. It is a rather involved data structure with all kinds of interesting things going on. Unfortunately I cannot put together a minimal working example that will cause a Python hang. -- _

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Richard Oudkerk added the comment: What type of object did you try to send, and how can the problem be reproduced? There are plenty of types which don't support pickling, and where pickling only succeeds in producing invalid data which cannot be successfully unpickled. The exception raised w

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Changes by Antoine Pitrou : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

Changes by Ian Bell : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue15198] multiprocessing Pipe send of non-picklable objects doesn't raise error

New submission from Ian Bell : When a non-picklable object is sent through a multiprocessing.Pipe, no exception is raised, instead when trying to read the other end of the pipe, a TypeError is raised: TypeError: Required argument 'handle' (pos 1) not found -- components: Windows messa