Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable Python 2.6 & 3.x on Appveyor, fix builds on 3.x/MSVC #9

Merged
merged 3 commits into from
Aug 20, 2015

Conversation

moreati
Copy link
Contributor

@moreati moreati commented Aug 20, 2015

This makes Appveyor test the same range of Python versions as Travis.

Sorry for the ugly diff in appveyor.yml, it's a one time affair due to switching from https://github.com/pypa/python-packaging-user-guide/tree/master/source/code as the base to https://github.com/ogrisel/python-appveyor-demo. The later is better maintained.

Chocolately is the closest thing Windows has to Apt.
It's far more maintainable than the manual download/unzip I lashed up.
This commit pulls in the config from
https://github.com/ogrisel/python-appveyor-demo

Where maintenance of this technique seems to be coalescing.
This is not based on any understanding of C.
I've just applied the top results from Google:
 - libgit2/pygit2@39bb5de7
 - http:https://stackoverflow.com/a/9903698/293340
   > When you name your source files *.c, MSVC assumes it's compiling C,
   > which means C89. All block-local variables need to be declared at
   > the beginning of your functions.
LudovicRousseau added a commit that referenced this pull request Aug 20, 2015
Enable Python 2.6 & 3.x on Appveyor, fix builds on 3.x/MSVC
@LudovicRousseau LudovicRousseau merged commit 4105249 into LudovicRousseau:master Aug 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants