Conversation
| March 2026. The release of pandas 3.0 has broken a number of things in ``fastparquet``. Since pandas now | ||
| depends explicitly on pyarrow, there is no longer any demand for the existence of this project, and it |
There was a problem hiding this comment.
Note that this is not entirely correct (depending on how you interpret "depends explicitly"): pyarrow is not a required dependency of pandas, it is still an optional dependency, even for pandas 3 (we did start to use it by default for more features, though, i.e. if available it will be used for the default string dtype, but there is still a fallback implementation without pyarrow as well)
There was a problem hiding this comment.
Thanks Joris. I did notice that the dep wan't in fact there, although it was heavily talked about as coming with 3.0 . I certainly was surprised! I assume it's coming?
I any case, to fix fastparquet to work correctly with Str input (which would either mean converting to objects first, which is very costly, or reading arrow buffers directly, which seems outside of fastparquet's remit) seems a step too far given that other things also broke around the index and time types.
No description provided.