replacement for nntplib on Python3
I used to use a script that relied on nntplib, which is currently still available in Python3 but scheduled for deprecation in the near future. What would be a suitable replacement? -- Retrograde -- https://mail.python.org/mailman/listinfo/python-list
Re: What to use instead of nntplib?
> > Yes, me for one, a good newsreader is really a wonderful way to manage > > technical 'lists' like this one. > > IMO, there's nothing better. Newsreaders were designed from the > beginning to deal with the sort of traffic and usage patterns seen in > mailing lists. Using an MUA (even combined with something like > procmail) and folders/labels is just a pale imitation of a good > newsreader. > > > Usenet news is still very much alive though a minority interest now > > I suspect. > > This list's decision to stop accepting postings via news.gmane.io is > what prompted me to write my own "inews" application in Python that > uses SMTP for some groups and NNTP for others when I "post" via slrn. > > I probably use NNTP more to access mailing lists via gmane than I use > it for accessing the "real" Usenet groups. > > NNTP is not just for Usenet... I asked this question in February and got the same response. But on news.software.readers 16 May, Ted Heise posted a useful perl script. I'm starting to think I'll move to Perl for Usenet posting; I have yet to find a Python solution easy enough for this non-technical user. -- https://mail.python.org/mailman/listinfo/python-list
Re: What to use instead of nntplib?
> >> See PEP 594: https://peps.python.org/pep-0594/ > > > > Thanks Cameron. > > A scary list; I must have a dozen projects from the late 90s still > > live that are using many of these! I'm glad I'm retired and won't > > be the one who has to fix 'em :-) > > It has been pointed out to me that Perl still has a supported NNTP > library. That stung. However, it's a CPAN module, which is more > equivalent to PyPI than to the standard library, so I guess that it > isn't as bad a loss of face as I feared. I'm latching onto this thread just so I can bitch: I always thought "Batteries included" was a great concept, a great philosophy, a great slogan. It encouraged me to look into python because they made the tools available for you to do just about anything they want. Who ever came up with "Removing dead batteries" as a slogan, when some of those batteries still work perfectly well, needs to rethink it. Go ahead and remove code that no longer works, OK. But removing unpopular modules? That undercuts the entire philosophy of the platform, in my opinion. -- https://mail.python.org/mailman/listinfo/python-list
