[issue13520] Patch to make pickle aware of __qualname__

2013-11-29 Thread Alexandre Vassalotti
Changes by Alexandre Vassalotti : -- assignee: -> alexandre.vassalotti resolution: -> duplicate stage: patch review -> committed/rejected status: open -> closed superseder: -> Implement PEP 3154 (pickle protocol 4) versions: +Python 3.4 -Python 3.3 ___

[issue13520] Patch to make pickle aware of __qualname__

2012-08-21 Thread Richard Oudkerk
Richard Oudkerk added the comment: There is a cute way to use operator.attrgetter to produce backwards compatible pickles using the qualname: import pickle, copyreg, operator, sys, pickletools, types class AttrGetter(object): def __init__(self, name): self.name = name def __cal

[issue13520] Patch to make pickle aware of __qualname__

2012-06-24 Thread Hynek Schlawack
Changes by Hynek Schlawack : -- nosy: -hynek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue13520] Patch to make pickle aware of __qualname__

2012-02-26 Thread Łukasz Langa
Changes by Łukasz Langa : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue13520] Patch to make pickle aware of __qualname__

2012-01-22 Thread Hynek Schlawack
Changes by Hynek Schlawack : -- nosy: +hynek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue13520] Patch to make pickle aware of __qualname__

2011-12-06 Thread sbt
sbt added the comment: It looks like Issue 3657 is really about builtin methods (i.e. builtin_function_or_method objects where __self__ is not a module). It causes no problem for normal python instance methods. If we tried the getattr approach for builtin methods too then it should only be

[issue13520] Patch to make pickle aware of __qualname__

2011-12-05 Thread Alexandre Vassalotti
Alexandre Vassalotti added the comment: This might not be the case anymore, but __module__ can sometime be None. There is some discussion about this in Issue 3657. We should define the expected behavior when this happens. Also, I don't think backward-compatibility of the protocol is a big iss

[issue13520] Patch to make pickle aware of __qualname__

2011-12-02 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +alexandre.vassalotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue13520] Patch to make pickle aware of __qualname__

2011-12-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: > The attached patch makes pickle use an object's __qualname__ attribute > if __name__ does not work. > > This makes nested classes, unbound instance methods and static methods > picklable (assuming that __module__ and __qualname__ give the correct > "address")

[issue13520] Patch to make pickle aware of __qualname__

2011-12-02 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13520] Patch to make pickle aware of __qualname__

2011-12-02 Thread Ezio Melotti
Changes by Ezio Melotti : -- components: +Extension Modules stage: -> patch review type: -> feature request ___ Python tracker ___ _

[issue13520] Patch to make pickle aware of __qualname__

2011-12-02 Thread sbt
New submission from sbt : The attached patch makes pickle use an object's __qualname__ attribute if __name__ does not work. This makes nested classes, unbound instance methods and static methods picklable (assuming that __module__ and __qualname__ give the correct "address"). BTW, It would