> With the sudden flurry of emails about SpamBayes, I went ahead and created a new python3 branch at > > https://github.com/smontanaro/spambayes > > This is the result of a basic run of 2to3 nearly two years ago (!) followed by most functional changes to Neil Schemenauer's Python 3 partial port: > > https://github.com/nascheme/spambayes-core/ > > Nothing has been tested. I haven't even tried running anything yet. Given that I use Gmail, I suspect I will have to try getting the IMAP filter to run to make it semi-useful.
I'm focusing on sb_imapfilter, mostly because that is what would be most immediately useful to me (as a Gmail user). I fairly quickly got the app to start and launch its web server (in spambayes/Dibbler.py), then ran into a raft of byte/str problems. No surprise there, I suppose. After a few rounds of that (edit, run, poke a link, see a traceback, lather, rinse, repeat) I began to wonder if there was a better way. A couple things occur to me: - Is there a way to coax the server to — early on — decode incoming bytes as utf-8? - Would it be better to see about replacing the Dibbler, asyncore, and asynchat modules with stdlib modules? Note that the async* modules aren't even the old stdlib versions — may not even have anything in common with them other than their names. Any thoughts? Skip
_______________________________________________ spambayes-dev mailing list spambayes-dev@python.org https://mail.python.org/mailman/listinfo/spambayes-dev
