This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author cool-RR
Recipients alexandre.vassalotti, belopolsky, cool-RR, eric.araujo, exarkun, hinsen, lemburg, loewis, obamausa8, pitrou, rhettinger
Date 2011-02-23.14:53:53
SpamBayes Score 6.4051726e-08
Marked as misclassified No
Message-id <1298472841.36.0.379123010591.issue9276@psf.upfronthosting.co.za>
In-reply-to
Content
I also miss being able to pickle unbound methods on Python 3. I don't think there's an interest in pickling the actual code objects. In my opinion, unbound methods should be pickled exactly like all the other Python definitions, such as bound methods, top-level functions, and classes: They should be pickled by name.

IIUC, the challenge is how to figure out on which class an unbound method is defined. I'm using the term "unbound method" colloquially, I know it's implemented as a function. So perhaps Python needs to be changed to give unbound methods some attribute that will tell on which class they're defined?
History
Date User Action Args
2011-02-23 14:54:01cool-RRsetrecipients: + cool-RR, lemburg, loewis, rhettinger, hinsen, exarkun, belopolsky, pitrou, alexandre.vassalotti, eric.araujo, obamausa8
2011-02-23 14:54:01cool-RRsetmessageid: <1298472841.36.0.379123010591.issue9276@psf.upfronthosting.co.za>
2011-02-23 14:53:54cool-RRlinkissue9276 messages
2011-02-23 14:53:53cool-RRcreate