You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "jorisvandenbossche (via GitHub)" <gi...@apache.org> on 2023/02/16 15:29:23 UTC

[GitHub] [arrow] jorisvandenbossche commented on pull request #34184: GH-34154: [Python] Add `is_nan` expression

jorisvandenbossche commented on PR #34184:
URL: https://github.com/apache/arrow/pull/34184#issuecomment-1433268843

   > Is this expected?
   
   It's not super clear from the assert message, but so it is the "null" that is different (see my inline comment). As Alenka mentioned above, that is indeed expected (and tested on the C++ side) behaviour. 
   
   In general, predicate functions (checking something, returning a boolean) propagate nulls (in the idea of "you don't know the value, so you also don't know if it is NaN or not, so whether it should be True or False). 
   (one exception on that rule is of course `is_null` to check for nulls itself) 


-- 
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