Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #15421

Bug#1043240: transition: pandas 1.5 -> 2.1

From "Rebecca N. Palmer" <rebecca_palmer@zoho.com>
Newsgroups linux.debian.bugs.dist, linux.debian.maint.python
Subject Bug#1043240: transition: pandas 1.5 -> 2.1
Date 2024-01-21 16:40 +0100
Message-ID <HYI5r-4Bu8-1@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.

Show all headers | View raw


Control: severity 1053943 1053939 1053942 1044053 1044056 serious
Control: severity 1044074 1053946 1044078 1044079 1044077 serious
Control: severity 1044071 1044067 1044068 1044055 1044060 serious
Control: severity 1044072 1044073 1044064 1053945 1044054 serious
Control: severity 1044076 1053940 1044057 1053944 1050144 serious

As previously discussed in this bug, I'd like to move pandas 2.x into 
unstable reasonably soon.  I'm aiming to get it in before the Ubuntu 
24.04 freeze (in about a month), but I am open to disagreement on 
whether this is a good idea.

dask, python-skbio and python-upsetplot have been fixed since the 
previous discussion, but that still leaves the above 25.  6 of these 
have a known-to-me fix (dials influxdb-python python-altair 
python-feather-format seaborn tqdm - see their bugs for details).

Hence, doing this transition now would involve breaking some reverse 
dependencies with no known fix, but given the number of packages 
involved, trying to wait until they're all fixed is rather likely to 
instead end in pandas 1.5 being broken by a new Python/numpy/etc.

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


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