How about pypy?

[dholth]

Do you have any hints on getting pypy to work with this kind of setup?

[ogrisel]

I have not tried and I don't use PyPy personally.

The appveyor free workers would be too slow to build the full PyPy project itself but it could be interesting to test third party Python projects that have cffi-based compiled extensions and check that it runs correctly when used from a PyPy program under Windows.

[dholth]

I'd probably have to figure out how to download and install PyPy from appveyor.yml, ideally to the Users\Appveyor... cache, and just use that Python to run the same tests as the convenient Appveyor-provided ones.

[ogrisel]

You can reuse utility powershell functions from: https://github.com/ogrisel/python-appveyor-demo/blob/master/appveyor/install.ps1

[jayvdb]

#17 will make it easier to download the pypy installer.

[ogrisel]

#17 is now merged in master.

[anthrotype]

has anyone tried getting pypy to work on appveyor yet?

[dholth]

http://stackoverflow.com/questions/30822873/how-do-i-build-a-pypy-package-on-appveyor

Could probably be improved by caching into the appveyor home directory, to avoid downloading every single time.

[anthrotype]

I'll try! thank you 👍

[jayvdb]

It is a bit of a nightmare getting setuptools, tox, virtualenv & pip to all work on Windows with wheels and their vendoring of other packages and fresh bugs each release. I gave up with pypy3-2.4.0 and pypy-2.6.1, and manually installed setuptools for those, avoiding the other three.
Also it is critical to move the pypy unpacked directory out of the current build directory, otherwise setuptools and pkg_resources peek inside and fail to parse parts of the pypy distribution.

PyCQA/pyflakes#76

[ghost]

For future reference you can use chocolatey:

choco install python.pypy