Skip to content

Commit

Permalink
getting appveyor working
Browse files Browse the repository at this point in the history
  • Loading branch information
arm61 committed Aug 24, 2018
1 parent 6ac472c commit 6957be1
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions appveyor.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ environment:
# isn't covered by this document) at the time of writing.

- PYTHON: "C:\\Python27-x64"

MINICONDA: "C:\\Miniconda"
DISTUTILS_USE_SDK: "1"
- PYTHON: "C:\\Python34-x64"
DISTUTILS_USE_SDK: "1"
Expand All @@ -19,8 +19,9 @@ environment:

install:
# We need wheel installed to build wheels
- "%PYTHON%\\python.exe -m pip install wheel"
- "%PYTHON%\\python.exe -m pip install -r requirements.txt"
- "SET PATH=%MINICONDA%;%MINICONDA%\\Scripts;%PATH%"
- "python -m pip install wheel"
- "python -m pip install -r requirements.txt"
- "set PATH=%PATH%;C:\"%PYTHON%\\Scripts"

build: off
Expand All @@ -33,14 +34,14 @@ test_script:
# Note that you must use the environment variable %PYTHON% to refer to
# the interpreter you're using - Appveyor does not do anything special
# to put the Python version you want to use on PATH.
- "%PYTHON%\\python.exe setup.py test"
- "python setup.py test"

after_test:
# This step builds your wheels.
# Again, you only need build.cmd if you're building C extensions for
# 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct
# interpreter
- "%PYTHON%\\python.exe setup.py bdist_wheel"
- "python setup.py bdist_wheel"

artifacts:
# bdist_wheel puts your built wheel in the dist directory
Expand Down

0 comments on commit 6957be1

Please sign in to comment.