-
Notifications
You must be signed in to change notification settings - Fork 44
/
appveyor.yml
60 lines (51 loc) · 2.08 KB
/
appveyor.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
environment:
matrix:
# For Python versions available on Appveyor, see
# http://www.appveyor.com/docs/installed-software#python
# The list here is complete (excluding Python 2.6, which
# isn't covered by this document) at the time of writing.
# As of (2021-08-22) List now seems to be here
# https://www.appveyor.com/docs/windows-images-software/#python
- PYTHON: "C:\\Python36"
- PYTHON: "C:\\Python37"
- PYTHON: "C:\\Python38"
#- PYTHON: "C:\\Python39"
#- PYTHON: "C:\\Python36"
#- PYTHON: "C:\\Python33"
#- PYTHON: "C:\\Python33-x64"
# DISTUTILS_USE_SDK: "1"
#- PYTHON: "C:\\Python34"
#- PYTHON: "C:\\Python34-x64"
# DISTUTILS_USE_SDK: "1"
- PYTHON: "C:\\Python36-x64"
- PYTHON: "C:\\Python37-x64"
- PYTHON: "C:\\Python38-x64"
#- PYTHON: "C:\\Python39-x64"
install:
# We need wheel installed to build wheels
- "%PYTHON%\\python.exe -m pip install pip -U"
- "%PYTHON%\\python.exe -m pip install -r requirements.txt -U"
- "%PYTHON%\\python.exe -m pip install -e ."
build: off
test_script:
# Put your test command here.
# If you don't need to build C extensions on 64-bit Python 3.3 or 3.4,
# you can remove "build.cmd" from the front of the command, as it's
# only needed to support those cases.
# 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 -m pytest"
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
#- "build.cmd %PYTHON%\\python.exe setup.py bdist_wheel"
artifacts:
## bdist_wheel puts your built wheel in the dist directory
#- path: dist\*
#on_success:
# You can use this step to upload your artifacts to a public website.
# See Appveyor's documentation for more details. Or you can simply
# access your wheels from the Appveyor "artifacts" tab for your build.