pandas 3.0 is now available in experimental. As that version number
suggests, it can be a breaking change.
These packages appear to be broken *by* pandas 3.0: apache-arrow
azure-kusto-python beangrow bmtk boinor bqplot cfgrib cnvkit datalab
glueviz influxdb-python joypy json-tricks jsonpickle loki-ecmwf mdtraj
partd pybel pychopper pycoqc pymatgen-core pynwb pyranges pyrle
pytest-regressions python-altair python-anndata python-bioframe
python-bioregistry python-cgelib python-cobra python-dynasor
python-fluids python-pyani python-pyvista python-sigima python-upsetplot
python-vega-datasets q2-emperor q2-metadata q2-taxa r-bioc-mofa rpy2 slm
These packages have pre-existing failures (which are probably RC bugs,
but ones unrelated to this transition): asammdf dials emperor
ipython(sometimes) q2-diversity-lib q2-quality-filter traittypes umap-learn
Autopkgtest results:
https://qa.debian.org/excuses.php?experimental=1&package=pandas
Build test results (packages without (non-trivial) autopkgtests):
https://launchpad.net/~rebecca-palmer/+archive/ubuntu/pandas3p0/+builds?build_text=&build_state=failed
(And no, I don't know why many of these don't actually link to a log, or
whether they will start doing so if we wait longer.)
I suggest checking whether your upstream have already fixed this.
If that doesn't help, some common issues:
- The string dtype (separate from the object dtype) is now used by
default, and is not a numpy dtype
- pandas no longer depends on pytz - if you need it, you need to depend
on it explicitly
For more information, see the upstream release notes:
https://pandas.pydata.org/docs/whatsnew/v3.0.0.html
