sjperkins commented on issue #33997: URL: https://github.com/apache/arrow/issues/33997#issuecomment-1438928419
> But for extension types that are implemented in C++ externally (or for extension types that are implemented in Arrow C++, but for which we don't provide a custom python subclass), that doesn't work. I am wondering to what extent we want to allow "registering" a python class that should be used when wrapping a specific C++ extension type (and to what extent this would be useful for https://github.com/apache/arrow/blob/45918a90a6ca1cf3fd67c256a7d6a240249e555a/python/pyarrow/types.pxi#L1095-L1100 Perhaps one way to do this would be to modify `pyarrow.register_extension_type` to check for collision with an existing C++ Extension when calling `RegisterPyExtensionType`. If the name and storage type match, then the associated Python type can be registered in `_python_extension_types_registry`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
