You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is arguably more feedback than an issue / question, but while I was trying to use the DataFrame Interchange API I found the requirement of supporting custom sentinels as a consumer rather burdensome. As far as I understand, if the array describes itself as using a sentinel, then it is up the consumer to query describe_null() and convert that PyObject to whatever type works with the buffer.
For types that span multiple words (ex: 256 bit decimal), such a sentinel seems really hard if not impossible to support. Even for more primitive types, you have to jump through some hoops with the CPython API to do that translation.
Trying to support all of those cases in a lower level extension makes it a ton of effort to fully adhere to this specification
The text was updated successfully, but these errors were encountered:
This is arguably more feedback than an issue / question, but while I was trying to use the DataFrame Interchange API I found the requirement of supporting custom sentinels as a consumer rather burdensome. As far as I understand, if the array describes itself as using a sentinel, then it is up the consumer to query
describe_null()
and convert that PyObject to whatever type works with the buffer.For types that span multiple words (ex: 256 bit decimal), such a sentinel seems really hard if not impossible to support. Even for more primitive types, you have to jump through some hoops with the CPython API to do that translation.
Trying to support all of those cases in a lower level extension makes it a ton of effort to fully adhere to this specification
The text was updated successfully, but these errors were encountered: