[Stackless] Fwd: deepcopying (pickling) channels

John Ehresman jpe at wingware.com
Fri Oct 25 18:36:33 CEST 2013

On 10/25/13 11:44 AM, Kristján Valur Jónsson wrote:
> Did anyone attempt to patch pickle.py as suggested below, to diagnose the pickling problem?
> Once you arrive at a problem, it is useful to know the chain of objects it is working with.

Running in the debugger does break when the exception is raised.  It's 
raised when pickling the module due to a dictionary returned from a 
reduce function in the copy_reg.dispatch_table for module objects.  The 
reduce function is written in C (in Stackless/pickling/prickelpit.c) and 
gets the __import__ hook out of builtins.

I can probably fix the pickle error (I've hacked a fix locally), but the 
questions I have are essentially why is the __import__ hook saved and 
how/when is it used?  I worry that a fix for the pickling problem might 
lead to other, more obscure, problems later.



More information about the Stackless mailing list