After more testing, my code doesn't work. AppVeyor seems to come with Python 3.4 and 2.7 installed in their usual locations on drive C. I'm testing it out at My new file looks like this:

    - ps: (new-object net.webclient).DownloadFile('', 'C:/') # install pip
    - C:/Python34/python.exe C:/ # install pip part 2
    - C:/Python34/Scripts/pip.exe install wheel # install wheel
    - python build # or whatever
    - py.test # or something else
    - python sdist bdist_wheel upload

The build hasn't completed, though; I'm still waiting for the results. I keep making dumb mistakes with pytest. Status is at

On Sun, Sep 21, 2014 at 5:16 PM, Paul Moore <> wrote:
On 21 September 2014 22:47, Ryan Gonzalez <> wrote:
> I'm guessing the appveyor.yml file might look like this:
> install:
>   - cinst python
>   - cinst pip
>   - pip install wheel
> build: off # It's Python; no building allowed!
> test_script:
>   - py.test # or whatever to run tests
> deploy_script:
>   - python sdist bdist_wheel upload

The one I'm working from (cookiecutter) is more complex - essentially
because it manually installs Python etc. I'd not seen cinst before,
but from a quick search I see that's chocolatey. So yes, something
like that. Can you specify which version of Python cinst installs?
You'd actually want to make sure you had all the versions of Python
you supported installed.

Also, you probably couldn't do the upload in deploy_script unless you
were willing to store your credentials in AppVeyor.

But essentially, it's not hard to set up, AFAICT.

If anybody ever asks me why I prefer C++ to C, my answer will be simple: "It's becauseslejfp23(@#Q*(E*EIdc-SEGFAULT. Wait, I don't think that was nul-terminated."
Personal reality distortion fields are immune to contradictory evidence. - srean
Check out my website: