Replies: 1 comment
-
|
Thanks for opening this discussion, @tswast (apologies nobody has seen it yet) It seems like you're very clued in on the woes of
Yep, we're kinda dealing with this at the moment - but it is somewhat of a moving target (#3160 (comment))
These are all the import pandas as pd
# NOTE: `pandas>=3` only
pd.options.mode.nan_is_na = False
# NOTE: Not in `pandas-stubs`
pd.options.future.infer_string = True
pd.options.future.no_silent_downcasting = True
pd.options.mode.string_storage = "pyarrow"
pd.DataFrame().convert_dtypes(dtype_backend="pyarrow")
pd.Series().convert_dtypes(dtype_backend="pyarrow")Publicly we have Internally, this search will point you to where you can specify One last thing, while testing pytest --constructors='pandas[pyarrow],modin[pyarrow]' |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Context: I'd like to make a "bigframes" (BigQuery DataFrames) Narwhals backend (work-in-progress here: https://github.com/tswast/narwhals/commits/bigframes/)
While implementing this, the biggest roadblock I hit is with regards to dtypes. In general, BigFrames defaults to pyarrow as the default dtypes for multiple reasons.
I'm curious if it would be possible to make
_pandas_likebackends that use the pyarrow type system? Alternatively, maybe there's a way for a_pandas_likebackend to supply its own mapping from narwhals dtypes to pandas-y dtypes?Beta Was this translation helpful? Give feedback.
All reactions