rok commented on PR #34883: URL: https://github.com/apache/arrow/pull/34883#issuecomment-1503605774
> * For a specific use case, someone might not care about the permutation and just wants the physical C-contiguous array Wouldn't that not be possible with `tensor_ext_arr.storage.to_numpy()`? Or would that not be zero-copy? > * Because you want to do the handling of permutation / dim_names yourself, and therefore first want to get the numpy array as the physical array (see [GH-34882: [Python] Binding for FixedShapeTensorType #34883 (comment)](https://github.com/apache/arrow/pull/34883#issuecomment-1503146111) above for a possible reason for this, eg if you need to handle the potential combination of both permutation and/or dim_names, this might be easier to just all do yourself) How about we have pyarrow pass the permutation/strides information by default and have users use lower level API for manual handling of permutation / dim_names? I'm assuming underlying buffer doesn't get actually permuted in either case of course. -- 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]
