➜
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.
Created on 2003-11-04 06:58 by jemfinch, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg61129 - (view) | Author: Jeremy Fincher (jemfinch) | Date: 2003-11-04 06:58 | |
I just spent quite some time searching for documentation on the interface for __reduce__. Turns out, it's in the library documentation, 3.14.5.2, under the heading "Pickling and unpickling extension types." Perhaps that heading can be changed to more clearly indicate that "__reduce__ is documented here!" At least, when I'm writing new-style classes (which the pickle/copy machinery doesn't accept anything but a copy_reg registration or __reduce__ or __reduce_ex__) I don't generally consider my work to be an "extension class" and thus hadn't ever looked under that heading. |
|||
| msg61130 - (view) | Author: Raymond Hettinger (rhettinger) *  |
Date: 2003-11-28 17:54 | |
Logged In: YES user_id=80475 Would adding an index entry suffice? |
|||
| msg62770 - (view) | Author: A.M. Kuchling (akuchling) * |
Date: 2008-02-23 16:40 | |
Thanks for the suggestion. I've added index entries for __reduce__, as well as __reduce_ex__ and a few others in rev. 60994 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:00 | admin | set | github: 39501 |
| 2008-02-23 16:40:17 | akuchling | set | status: open -> closed resolution: fixed messages: + msg62770 nosy: + akuchling |
| 2003-11-04 06:58:38 | jemfinch | create | |