On Tue., May 21, 2019, 09:10 Christian Heimes, <christian at python.org> wrote: > On 21/05/2019 17.31, Antoine Pitrou wrote: > > > > As I said, if the main annoyance with nntplib is the sporadic test > > failures, then the relevant tests can be disabled on CI. > > > > NNTP itself is still used, even if less and less. > > I don't like the idea to drop a third of the test cases for nntplib -- and > the 30% that actually test that Python's NNTP library can talk to an actual > NNTP server. IMHO it's more beneficial for core development and for nntplib > to have it maintained by somebody that cares about the library. > Ditto for me. If the code isn't going to be properly tested then it's already unsupported, at which point we're back to wanting to deprecate it. -Brett > Even a deprecation in 3.8 means that the module has to be maintained until > EOL of 3.9, which is around 2026. > > Christian > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/brett%40python.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20190521/c1b68c07/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