PEP 594 – Removing dead batteries from Python's standard library

Re:PEP 594 – Removing dead batteries from Python's standard ... by mjevans on Wednesday May 22, 2019 @08:51PM (#19987253)

Does this mean we're going to have Python 2 installed on things forever? (Particularly anything that touches NNTP servers, as there's no replacement for that lib)

[ Parent | on HN ]

Re:PEP 594 – Removing dead batteries from Python's standard ... by viraptor on Wednesday May 22, 2019 @09:35PM (#19987504)

It's simple code. It can be moved to a separate package and imported with the same name.

[ Parent | on HN ]

Re:PEP 594 – Removing dead batteries from Python's standard ... by u801e on Thursday May 23, 2019 @05:20AM (#19989957)

If it's simple, then what's the point in removing it? Dealing with standard application level protocols like SMTP, NNTP, FTP, IMAP, POP, and HTTP shouldn't require installing third party packages.

[ Parent | on HN ]

Re:PEP 594 – Removing dead batteries from Python's standard ... by viraptor on Thursday May 23, 2019 @05:50AM (#19990138)

So that they can be improved / maintained. "stdlib is where packages go to die" is kind of true. You can use contact http from stdlib for example, but that's how we get urllib, urllib2, 3rd party urllib3 and requests.

For the point of removing the modules, check the "rationale" part of the PEP.

[ Parent | on HN ]

Re:PEP 594 – Removing dead batteries from Python's standard ... by u801e on Thursday May 23, 2019 @08:42AM (#19991118)

The original post you responded to mentioned that NNTP did not have a replacement, so I don't see how it could be improved/maintained if it's just not there anymore.

[ Parent | on HN ]

Re:PEP 594 – Removing dead batteries from Python's standard ... by earenndil on Wednesday May 22, 2019 @09:16PM (#19987402)

Which lib?

[ Parent | on HN ]

Re:PEP 594 – Removing dead batteries from Python's standard ... by anoncake on Thursday May 23, 2019 @02:02AM (#19988914)

The one for touching NNTP servers.

[ Parent | on HN ]