26.12.17 12:16, Hugh Fisher пише: > I have a Python program which generates the boilerplate code for > native extension modules from a Python source definition. > (http://bitbucket.org/hugh_fisher/fullofeels if interested.) > > The examples in the Python doco and the "Python Essential Reference" > book all use a statically declared PyTypeObject struct and > PyType_Ready in the module init func, so I'm doing the same. Then > Python 3.5 added a check for statically allocated types inheriting > from heap types, which broke a couple of my classes. And now I'm > trying to add a __dict__ to native classes so end users can add their > own attributes, and this is turning out to be painful with static > PyTypeObject structs > > Would it be better to use dynamically allocated type structs in native modules? Yes, you can create heap types by using PyType_FromSpecWithBases(). But be aware of caveats (https://bugs.python.org/issue26979).
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