You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/07/07 06:40:05 UTC

[GitHub] [arrow] chaubold commented on pull request #13454: ARROW-13612: [Python] Allow specifying a custom type for converting ExtensionScalar to python object

chaubold commented on PR #13454:
URL: https://github.com/apache/arrow/pull/13454#issuecomment-1177154061

   @jorisvandenbossche that sounds to me like the question whether it will ever make sense that an `ExtensionScalar` has a state. If it does, then it might make sense to give the user full control by providing `ExtensionScalar` subclasses. However, if the assumption is that a `Scalar` doesn't have a state on its own (which is at least my understanding), then having the conversion method `scalar_as_py()` in the `ExtensionType` and using that whenever accessing the elements of an `ExtensionArray` with that `ExtensionType` sounds good enough to me (looking at it from a user perspective).


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org