@martindurant I see you added a notice of retirement of fastparquet (dask/fastparquet#973). pandas 3 doesn't explicitly (yet) depend on pyarrow, but if you anticipate no further fastparquet development, I suppose pandas could just use pyarrow's parquet reader as I imagine there's a lot of overlap between the two now(?)
Generally if engine="fastparquet" is deprecated and removed, the engine keyword can be deprecated itself (along with the io.parquet.engine option)
@martindurant I see you added a notice of retirement of fastparquet (dask/fastparquet#973). pandas 3 doesn't explicitly (yet) depend on pyarrow, but if you anticipate no further fastparquet development, I suppose pandas could just use pyarrow's parquet reader as I imagine there's a lot of overlap between the two now(?)
Generally if
engine="fastparquet"is deprecated and removed, theenginekeyword can be deprecated itself (along with theio.parquet.engineoption)