[Python-Dev] PEP 594: Removing dead batteries from the standard library (original) (raw)

André Malo nd at perlig.de
Tue May 21 07:39:44 EDT 2019

On Dienstag, 21. Mai 2019 13:24:34 CEST Victor Stinner wrote:

Le mar. 21 mai 2019 à 13:18, André Malo <nd at perlig.de> a écrit : > There's software in production using both. (It doesn't mean it's on pypi > or even free software). > > What would be the maintenance burden of those modules anyway? (at least > for nntp, I guess it's not gonna change).

The maintenance burden is real even if it's not visible. For example, testnntplib is causing frequently issues on our CI: https://bugs.python.org/issue19756 https://bugs.python.org/issue19613 https://bugs.python.org/issue31850 It's failing frequently since 2013, and nobody managed to come with a fix.. in 6 years. There are 11 open issues with "nntp" in their title (8 with exactly "nntplib" in their title). testnntplib uses the public server news.trigofacile.com which is operated by Julien ÉLIE. Two years ago, Julien asked me if there is any plan to support the NNTP "COMPRESS" command.

So what I hear is, this battery is definitely not dead, which is what the PEP is all about. it's just half charged (or discharged, depending on your POV), so to speak.

Substitute: "none" should read pypi then?

nd

"Solides und umfangreiches Buch" -- aus einer Rezension

<http://pub.perlig.de/books.html#apache2>

More information about the Python-Dev mailing list