On Tue, 21 May 2019 at 04:30, Antoine Pitrou <solipsis at pitrou.net> wrote: > > NNTP is still quite used (often through GMane, but probably not only) so > I'd question the removal of nntplib. I concur nntplib should be left alone. There are possibly even less used network protocols such as telnet (tenetlib) which are not targeted by this PEP but could have been by following the same logic. FTP is another one that despite no longer popular, still has a constant user base (you’d be surprised by the amount of traffic we got over FTP in the last company I worked for). Overall, I think the bar for a module removal should be set very high, especially for “standard” things such as these network protocols, that despite being old are not likely to change. That means that also the maintenance burden for python-dev will be low or close to none after all. It seems to me also spwd/crypt modules fall into this category (all UNIX platforms have the shadow password db, which is nice to have in python out of the box). In that case the removal appears to be more justified by the security implications than them being not widely used though, so I would use more caution and treat them differently (eg. opt for doc warning + investigate a possible replacement). Also note that spwd could be used to parse /etc/passwd, despite I admit its primary use case is password checking. Certain users may even not care about the additional security provided by PAM (eg. internal devop scripts). -- Giampaolo - http://grodola.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190522/ee31537c/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4