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


Groups > linux.debian.maint.python > #14953 > unrolled thread

Bug#1031701: python3-pandas: Pandas requires version '2.0.1' or newer of 'xlrd'

Started by"Rebecca N. Palmer" <rebecca_palmer@zoho.com>
First post2023-02-27 09:00 +0100
Last post2023-02-27 09:00 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1031701: python3-pandas: Pandas requires version '2.0.1' or newer of 'xlrd' "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2023-02-27 09:00 +0100

#14953 — Bug#1031701: python3-pandas: Pandas requires version '2.0.1' or newer of 'xlrd'

From"Rebecca N. Palmer" <rebecca_palmer@zoho.com>
Date2023-02-27 09:00 +0100
SubjectBug#1031701: python3-pandas: Pandas requires version '2.0.1' or newer of 'xlrd'
Message-ID<G3GAp-8O0x-7@gated-at.bofh.it>
I don't consider the lack of .xls in pandas worth a freeze exception, 
but consider it reasonable for others to disagree with that.

As noted in the bug, there are some (possibly not-technically-valid) 
.xlsx files that xlrd 1 can open but openpyxl can't - _pandas_ won't be 
able to open those either way, but allowing other applications to do so 
is still worth something.

There also may be applications that could switch to openpyxl but simply 
haven't.  I don't know how much effort switching is / whether it would 
be reasonably possible for us to do it.

However, I wasn't aware of the security issues in xlrd 1 when I wrote 
that, and they may well be a reason to go to xlrd 2 and accept this 
breakage.  Are they the long-standing "denial of service via excessive 
XML entity expansion" or is there now (also) a risk of something worse?

[toc] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web