[ 
https://issues.apache.org/jira/browse/ARROW-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16870879#comment-16870879
 ] 

Artem KOZHEVNIKOV commented on ARROW-5208:
------------------------------------------

Just curiosity question : what was the reasons to have `python_to_arrow.cc` 
module in pure c++ and not in cython let say ? (To be honest, I did not feel 
myself confortable enough to contribute in c++...)

Passing mask argument into `InferArrowType` will also solve the case 
`_is_array_like(obj) is True` (or in this case the inference is based on pandas 
) ?

> [Python] Inconsistent resulting type during casting in pa.array() when mask 
> is present
> --------------------------------------------------------------------------------------
>
>                 Key: ARROW-5208
>                 URL: https://issues.apache.org/jira/browse/ARROW-5208
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>    Affects Versions: 0.13.0
>            Reporter: Artem KOZHEVNIKOV
>            Assignee: Wes McKinney
>            Priority: Major
>             Fix For: 0.14.0
>
>
> I would expect Int64Array type in all cases below :
> {code:java}
> >>> pa.array([4, None, 4, None], mask=np.array([False, True, False, True]))   
> >>>                                                                           
> >>>      
> <pyarrow.lib.Int64Array object at 0x91fad3a98> [4, null, 4,  null ]
> >>> pa.array([4, None, 4, 'rer'], mask=np.array([False, True, False, True]))  
> >>>                                                                           
> >>>         
> <pyarrow.lib.Int64Array object at 0x9201f23b8> [4, null, 4,  null ]
> >>> pa.array([4, None, 4, 3.], mask=np.array([False, True, False, True]))     
> >>>                                                                           
> >>>          <pyarrow.lib.DoubleArray object at 0x91fab7638> [   4,   null,   
> >>> 4,   null ]{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to