[issue18068] pickle + weakref.proxy(self)

2015-11-28 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: The weakref.proxy object delegates all attribute access to referred object, including special attributes used in pickling, like __class__ or __getstate__. test.recursive is not test, but it looks as TestPickle instance for the pickler. It is pickled and unpi

[issue18068] pickle + weakref.proxy(self)

2013-10-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: I don't think weakref objects are meant to be picklable at all. At least there's no support code for that, so pickling weak proxies only works by chance. -- nosy: +alexandre.vassalotti type: behavior -> enhancement versions: +Python 3.4 -Python 2.6, Pyt

[issue18068] pickle + weakref.proxy(self)

2013-10-14 Thread Georg Brandl
Changes by Georg Brandl : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue18068] pickle + weakref.proxy(self)

2013-05-26 Thread Oleg Broytman
New submission from Oleg Broytman: Hello! I've found a problematic behaviour of pickle when it pickles (direct or indirect) weak proxies to self. I suspect pickle cannot detect reference loops with weak proxies. I managed to narrow the case to the following example: import pickle, weakref class