René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"clarify separation between rust code and python wrappers","articleBody":"#750 added `python` wrappers instead of directly exposing `pyo3` generated code.\r\n\r\nWe should leverage that to clean up and improve the rust codebase by:\r\n\r\n1) Letting `python` wrappers handle any aliases.\r\n2) Letting `python` wrappers handle any argument defaults, removing `#[pyo3(signature(...))]` annotations from the Rust codebase\r\n\r\nAdditionally, we should provide guidance so that contributors understand the separation. \r\n\r\n@timsaucer [recommends](https://github.com/apache/datafusion-python/pull/771#discussion_r1693020654) the following guidelines (and I agree):\r\n\r\n\u003e I think it's worth adding some guidance about what to put in python vs what to put in rust for this repo. In my mind the things that should go into the python side are\r\n\u003e \r\n\u003e     * Trivial aliases (this is a good example)\r\n\u003e     * Simple type conversion, like path -\u003e string of the path or number to lit(number)\r\n\u003e     * More complex type conversion if it makes sense to do in python. For example, in the named_struct where sending in a dictionary on the python side makes a lot more sense and isn't as simple to do via pyo3.\r\n\u003e \r\n\u003e And then I'd lean towards everything else sitting on the rust side.\r\n\u003e ","author":{"url":"https://github.com/Michael-J-Ward","@type":"Person","name":"Michael-J-Ward"},"datePublished":"2024-07-26T15:52:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/779/datafusion-python/issues/779"}