[Ipython-tickets] [IPython] #230: changed behavior when push function object in r3021?

[IPython]

#230: changed behavior when push function object in r3021?
----------------------+-----------------------------------------------------
 Reporter:  yichun    |        Owner:  bgranger
     Type:  defect    |       Status:  assigned
 Priority:  normal    |    Milestone:          
Component:  ipython1  |      Version:          
 Severity:  normal    |   Resolution:          
 Keywords:            |  
----------------------+-----------------------------------------------------
Comment (by yichun):

 Thanks for explanation. Looking forward to see the changes.
 Would pushFunction/pullFunction be different with push/pull previously we
 have, in what aspect? Is the closure functions able to be pushed into
 engines with current implemantation?

 Replying to [comment:2 bgranger]:
 > Starting in r3012, push and pull cannot be used for moving functions to
 engines and back.  Instead, there are new dedicated methods in the
 interface (pushFunction/pullFunction) that should be used for this
 purpose.  This choice was made because the generality of push/pull did not
 allow for a truly robust handling of functions (which aren't really
 pickelable).  We need to add new logic to push/pull that raises a more
 informative exception when a user tries to push/pull a function.  It
 should raise something like:
 >
 > TypeError("push/pull don't work with functions, use
 pushFunction/pullFunction instead")
 >
 > Just a warning, we are getting close to merging in a new set of changes
 that will change the API in more dramatic ways.  Watch the ipython lists
 for details.

-- 
Ticket URL: <http://ipython.scipy.org/ipython/ipython/ticket/230#comment:3>
IPython <http://ipython.scipy.org>
The IPython interactive Python system