paleolimbot commented on issue #435: URL: https://github.com/apache/arrow-nanoarrow/issues/435#issuecomment-2066896629
These are all good points...I definitely only spent the minimum required time on these reprs. The `ast` module has `ast.dump()` (independent of the `repr()` of any particular item), would that be a good place for something like this? Something like `nanoarrow.dump()` might take the pressure of the `repr()`s so that they could be more compact...one of the issues with them right now is that they are awful in the debugger because of all the line breaks (but maybe there's no way around that without making them considerably un-useful). The `CArrayView` causes a bit of confusion because it's *almost* a `pyarrow.Array`...its actual purpose is a tool for validation and to minimize the overhead of iterating over many arrays of the same type. Its purpose was extended slightly in the Python bindings, but I am not particularly keen to funnel users to anything other than the `nanoarrow.Array` (while funneling developers to the raw C struct wrappers or iterators). -- 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]
