You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an add-on to this, does it make sense to name the .to_df() method more explicitly such that the user knows it references pandas (for when polars is fully supported in the future)? There is already a .to_pandas() method in the table API, which I assume was named this way for this very reason. .to_df() is ambiguous for a framework that supports both pandas and polars dataframes. In the longer run, it would be awesome to use .to_arrow(), .to_pandas() or .to_polars(), for both the table and query result APIs, to keep things consistent and easy to remember.
Currently we only support
.to_df()
on the Query object.The text was updated successfully, but these errors were encountered: