Abhinav0905 commented on issue #50604: URL: https://github.com/apache/arrow/issues/50604#issuecomment-5320291028
I can work on a prototype once the intended contract is confirmed. My initial preference is option 1: keep `ExtensionScalar.as_py` as the nested customization point, treat an `Array.to_pylist` override as top-level behavior, and document that distinction explicitly. I would add parity tests covering extension children under both list and struct parents so the behavior is consistent rather than accidental. That approach also keeps the bulk conversion path fast. If option 2 is preferred, I can instead prototype explicit override detection and benchmark nested conversion to quantify the dispatch cost. Would maintainers prefer the documented scalar-customization contract or preservation of nested array overrides? -- 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]
