Well, it is nice to have official confirmation that the tweaks I made to get tests passing on AppVeyor didn't break Travis, at least. Opening the PR might have fixed AppVeyor's stuck queue, it seemsNope, the queue is still stuck, but I'm done for the night anyway. It's almost 3am.

Meanwhile, if anyone can tell me why the python -c 'import struct; print struct.calcsize("P") * 8' command is causing a parse error, I'd appreciate the pointer. (It's mostly for debugging the builds, because I'm not convinced AppVeyor actually gives us 64-bit Windows. Based on my experience, pyenchant should fail to install on Windows x64, and it worked just fine in previous test builds.)

The tests pass on AppVeyor, but at least the 64-bit jobs should be failing due to pyenchant. I don't really want to merge this until the jobs we expect to fail, fail. But I suspect my patience will last only so long… and even if it doesn't catch the Windows problem we know about it would still be nice to have AppVeyor catching whatever issues it can on new PRs and such.

I know what's happening now, thanks to a push from AppVeyor support and a little digging. PyEnchant bundles libraries for Windows, but the install failures I and other have seen occurred under MSYS2.

This AppVeyor config can be further extended to also test on MSYS2 (which is supported)…or we can just say MSYS2 is not a supported environment for Sopel. I'd like to support it—ideally Sopel should run anywhere Python is available. I will dig some more before finalizing this configuration.

ideally Sopel should run anywhere Python is available

Yeah... except for some command options, like fork, because Windows does not support os.fork().

So, this beg the question: do we want to support Windows? If so, I'd push even more for dropping old version of Python, because the matrix support would be already quite huge.

Well, you know… "run" doesn't mean "all features work identically". 😛

You've already seen the Python version-support plans for the next couple of releases, so don't worry—py2 will go away Real Soon Now™ and we can stop bothering with it. Actually, I decided to bump this into Sopel 8, which is currently planned to drop several old Python versions.

Six months later, I think I'll abandon this. During the dev cycle for Sopel 8, we'll probably switch from Travis to GitHub Actions. Even if we don't switch, Travis has Windows environments available. No matter what, we'll be able to test on Windows in the same CI tool as Linux builds.