It seems I might have successfully built a Windows installer using the Appveyor continuous integration platform. I don't have direct access to Windows, however I was able to run the installer without error using WINE, and start up the POP3 proxy. I've not tried to go any farther.
I'm looking for a Windows user who would like to help wring out the remaining bugs. If you can give it a whirl, the installer to test is here: https://ci.appveyor.com/api/buildjobs/dg5ewclrsvyiubnh/artifacts/spambayes%2Fwindows%2Fspambayes-1.1b3.exe This includes the most recent changes to SpamBayes and embeds Python 2.7.14. If you try it out and find problems, let me know. You can also fork the project on GitHub: https://github.com/smontanaro/spambayes/ and produce pull releases with putative changes. I'm working from the "appveyor" branch. The appveyor.yml file is right at the top level. I'm sure it's a mess. That's what happens when the developer knows nothing about Windows and the only way to test anything is to push a commit. (74 pushes...) 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
