[I wrote:] > One property of types that do not have define HEAPTYPE is that their > __module__ attribute is always __builtin__. This makes them > mighty hard to > pickle. It further suggests that every type that isn't a builtin type > should define HEAPTYPE. I don't think I made much sense above. I meant to say: When my C types didn't define HEAPTYPE, it was impossible to pickle them. When I added the HEAPTYPE and defined __safe_for_unpickling__ as a data member, it became possible to pickle instances of those types. It was far from obvious, though, that I needed to do those two things to make pickling work. Jeremy
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4