I’m updating my C++ code to use PointerTo<>
to track references of objects, but I hit an unexpected issue when integrating it with my Python code.
When passing a vanilla pointer, it seems that generated wrapper automatically converts Py_None
to nullptr
. On the other hand if I switch to PointerTo<>
the wrapping code raises an error as it can not convert Py_None
to the base class referenced in PointerTo<>
. Is there a way to indicate to interrogate that Py_None
should be allowed (and mapped to nullptr
?).