The ebcdic package released v2.0.0 earlier this year, but requirements.txt currently caps it at <2 (ebcdic>=1.1.1,<2).
Per the upstream changelog, 2.0.0 is "a pure technical release that does not change the functionality of the package" — it only modernizes the build toolchain and drops support for Python 2 and Python 3.8. Because extract_msg still supports Python 3.8 (per setup.py and the CI matrix), the safest fix is to widen the upper bound rather than require ebcdic 2.x outright. On Python 3.8 pip will continue to resolve to ebcdic 1.1.1; on Python 3.9+ it can pick up 2.x.
This is analogous to #469 for beautifulsoup4.
I'll open a PR shortly.
The
ebcdicpackage released v2.0.0 earlier this year, butrequirements.txtcurrently caps it at<2(ebcdic>=1.1.1,<2).Per the upstream changelog, 2.0.0 is "a pure technical release that does not change the functionality of the package" — it only modernizes the build toolchain and drops support for Python 2 and Python 3.8. Because
extract_msgstill supports Python 3.8 (persetup.pyand the CI matrix), the safest fix is to widen the upper bound rather than require ebcdic 2.x outright. On Python 3.8 pip will continue to resolve toebcdic 1.1.1; on Python 3.9+ it can pick up2.x.This is analogous to #469 for
beautifulsoup4.I'll open a PR shortly.