bingbong-sempai
bingbong-sempai
yeah i agree that too many aliases is a bad thing. it's just that pairing `read_` and `write_` (same with `from_` and `to_`) feels like the "correct" thing to do.
that's unfortunate, i was hoping ibis would be able to make API changes that pandas couldn't
an option can be to alias `read_` to `from_` instead? `from_` can cover both read and scan operations. that way io could pair `from_` and `to_`.
Just to add, both Polars and DuckDB use `write_parquet` and not `to_parquet`.
Ah yeah, adding prefixes to all struct fields would also solve the `DuplicateError`. But it seems like an expensive operation since all nested structs have to be edited Compared to...
This is how it can look like if an index parameter is added: Description | Parameters -- | -- Drop duplicate indices only | subset=None, index=True Drop duplicate columns only...
> I'm personally leaning towards option 2 which basically treats the index as a value of the row Same, I think this is what most people would expect.