jorisvandenbossche commented on PR #34883: URL: https://github.com/apache/arrow/pull/34883#issuecomment-1503499447
> `pyarrow->numpy` conversion should (imo) use permutation data to create ndarray with correct strides while using the same physical layout (zero-copy) of the data buffer. I don't see any good reason to not do this in pyarrow but I might be missing something? @rok see my comments above? _Potential_ reasons that someone might not want to have the permuted ndarray: - For a specific use case, someone might not care about the permutation and just wants the physical C-contiguous array - 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 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) -- 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]
