Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15344
| From | Matthias Klose <doko@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.maint.python |
| Subject | Bug#1043240: transition: pandas 1.5 -> 2.1 |
| Date | 2023-12-11 08:20 +0100 |
| Message-ID | <HJIK5-cMHO-3@gated-at.bofh.it> (permalink) |
| References | <HJs2B-cCzh-1@gated-at.bofh.it> <H0eoN-ctw-9@gated-at.bofh.it> <HJs2B-cCzh-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
On 10.12.23 14:06, Rebecca N. Palmer wrote: > I'd like to move forward with the pandas 1.5 -> 2.1 transition > reasonably soon. > > Given that pandas 2.x is *not* required for Python 3.12 (but is required > for Cython 3.0), should we wait for the Python 3.12 transition to be > done first? > > These are broken by pandas 2.x and have a possible (but untested) fix in > their bug - please test and apply it: > dask(?) dials influxdb-python* python-altair python-feather-format > python-upsetplot seaborn tqdm* > (* = this package is currently also broken for a non-pandas reason, > probably Python 3.12, that I don't have a fix for) > > These are broken by pandas 2.x and have no known-to-me fix: > augur cnvkit dyda emperor esda mirtop pymatgen pyranges python-anndata > python-biom-format python-cooler python-nanoget python-skbio python-ulmo > q2-quality-control q2-demux q2-taxa q2-types q2templates sklearn-pandas > Some generic things to try are pandas.util.testing -> pandas.testing, > .iteritems() -> .items(), and if one exists, a more recent upstream > version. > > Is this an acceptable amount of breakage or should we continue to wait? > Bear in mind that if we wait too long, we may be forced into it by some > transition further up the stack (e.g. a future Python or numpy) that > breaks pandas 1.x. up to the maintainers. But please wait at least until the current pandas and numpy migrated to testing, e.g. that the autopkg tests of pandas and numpy triggered by python3-defaults pass. Is there a way to see the binNMUs which are still stuck in unstable, and don't migrate? Matthias
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1043240: transition: pandas 1.5 -> 2.1 "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2023-12-10 14:30 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Julian Gilbey <jdg@debian.org> - 2023-12-10 21:30 +0100
Bug#1043240: pandas 1.5 -> 2.1? "Kingsley G. Morse Jr." <kingsley@loaner.com> - 2023-12-10 22:10 +0100
Bug#1043240: pandas 1.5 -> 2.1? Drew Parsons <dparsons@debian.org> - 2023-12-11 00:40 +0100
Bug#1043240: pandas 1.5 -> 2.1? Julian Gilbey <jdg@debian.org> - 2023-12-11 11:10 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Matthias Klose <doko@debian.org> - 2023-12-11 08:20 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Matthias Klose <doko@debian.org> - 2023-12-11 18:40 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2024-01-21 16:40 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Andreas Tille <andreas@an3as.eu> - 2024-01-21 19:40 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Stelios Moschos <stel.moschos@gmail.com> - 2024-01-21 20:40 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Julian Gilbey <julian@d-and-j.net> - 2024-01-22 13:20 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2024-01-22 22:00 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Julian Gilbey <julian@d-and-j.net> - 2024-01-23 13:40 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Graham Inggs <ginggs@debian.org> - 2024-01-26 07:50 +0100
Bug#1043240: transition: pandas 1.5 -> 2.1 Julian Gilbey <julian@d-and-j.net> - 2024-01-26 08:40 +0100
csiph-web