I'm in favor of getting rid of the Python 2.2 compatibility. It just clutters up the code with a bunch of try/except statements. Is there realistically still a sizable enough population of SpamBayes users still stuck on Python 2.2? My inclination is to jump to compatibility with Python 2.4.
Also, as I've been horsing around the past week or two trying to add some new functionality and clean up some stuff I noticed we have *a lot* of code squirreled away in subversion which is probably no longer used by anybody. I'm in favor of starting to dump unused code to reduce the maintenance overhead after we shove 1.1 (kicking and screaming) out the door. Finally, I'm planning on incorporating the ThunderBayes code into SpamBayes. It's no longer supported by the original author. He and I exchanged some emails awhile ago. He was fine with the idea. This would allow us to at least get a ThunderBayes version out there which uses SpamBayes 1.1. It would still be essentially unsupported unless and until we can scrounge up some bodies to actually maintain it. Still, unsupported ThunderBayes using SpamBayes 1.1 seems better to me than unsupported ThunderBayes using SpamBayes 1.0. Comments? Skip _______________________________________________ spambayes-dev mailing list spambayes-dev@python.org http://mail.python.org/mailman/listinfo/spambayes-dev
