homepage

The attached script (picklecycle.py) gives me an
assertion error
in Pickler.memoize(). Maybe I'm just doing something dumb.
I have very little experience with pickle and even less
experience
pickling new-style class instances. I'm just trying to
adapt an
existing messy object graph to allow it to be pickled.
 I realize the
two instances refer to each other, but I thought pickle was
supposed to gracefully handle cyclic object graphs.
I can worm around the problem a couple ways. First,
getting
rid of new-style classes does the trick. Also
modifying B.__reduce__
to not return self.__dict__ seems to do the trick.
Output (cycle.out) and a modified version of
Pickler.memoize
(memoize.py) will be attached momentarily.

Logged In: YES 
user_id=44345
Attaching chatty version of Pickler.memoize()

Logged In: YES 
user_id=44345
Attaching the output I see when running picklecycle.py w/ the
modified memoize() method (cycle.out).

Logged In: YES 
user_id=147070
it does memoize recursively, 
but "asserts" not to get stuck in cycles.
that's how i understand the code if ::
 assert id(obj) not in self.memo
is replaced by ::
 if id(obj) in self.memo:
 return
it works (better). and test_pickle.py still passes.

This bug can be reproduced very easily:
 import pickle
 class MyClass(object):
 pass
 
 m = MyClass()
 m2 = MyClass()
 s = set([m])
 m.foo = set([m2])
 m2.foo = s
 print pickle.dumps(s)
This bug is critical as the pure-python pickle module is required when
trying to remove warnings in -3 mode with Python 2.6, which is something
that will be very common in the near future. It's easily reproducible
with simplistic object cycles like that of the above, in 2.5, 2.6 and
3.0 at least.

im noticing my test case seems to work fine in py 3.0.1. haven't
tested 2.6.2.

This looks like a duplicate of issue 1581183. The issue is still present in py3k, but only shows up in picklecycle.py when using pickle.py version. I am attaching picklecycle3.py which is py3k version of picklecycle.py using python pickler.

There are two issues here. The original issue is a duplicate of #1062277. The other issue is specific to cycles containing a set. [msg77200]
I am opening a separate issue for that. See #9269.