SpamBayes has never been ported to Python 3.x. I doubt it would be terribly difficult, especially with some of the ancillary tools available like futurize, six and 2to3. Pull requests against
https://github.com/smontanaro/spambayes welcome. S On Mon, Nov 27, 2017 at 1:40 PM, Dale Schroeder <d...@briannassaladdressing.com> wrote: > On 11/23/2017 1:21 PM, Skip Montanaro wrote: >>> >>> Skip, thanks for the news. What would be the symptoms of that particular >>> bug? >> >> The tokenizer was generating certain tokens which it assumed would be >> dotted quads (e.g., 73.73.103.110) but not checking that they actually >> contained four elements. The result was an IndexError exception. This >> error could only be triggered if you had either x-mine_nntp_headers or >> x-lookup_ip set to True. My fingerprints are on the relevant bit of >> code, so mea culpa. >> >> Skip >> _______________________________________________ >> SpamBayes@python.org >> https://mail.python.org/mailman/listinfo/spambayes >> Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes >> Check the FAQ before asking: http://spambayes.sf.net/faq.html > > Skip, > > I was able to compile and run the new version with no problems under Python > 2.7. Just for fun, I tried running with Python 3.6 and had no success. So, > I am wondering if it's something I did wrong or the possibility that > Spambayes just doesn't work with Python 3.x? Perhaps, the dependencies > change with Python 3, too. This is on Debian Buster. > > Thanks for any info. > > Dale > > _______________________________________________ SpamBayes@python.org https://mail.python.org/mailman/listinfo/spambayes Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
