-
Notifications
You must be signed in to change notification settings - Fork 26
/
appveyor.yml
50 lines (42 loc) · 1.59 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
build: false
environment:
MINICONDA: C:\Miniconda3
PYTHON_ARC: "64"
matrix:
- PYTHON_VERSION: 3.10
- PYTHON_VERSION: 3.11
init:
- "ECHO %PYTHON_VERSION% %MINICONDA% %PYTHON_ARC%"
install:
- mkdir C:\Users\appveyor\.conda
- call %MINICONDA%\Scripts\activate.bat
- conda config --set always_yes yes --set changeps1 no
- conda update -q conda
- conda info -a
- conda env create -f github_actions_environment.yml python=%PYTHON_VERSION%
- activate cellpy_dev
test_script:
- pytest
#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.
# - "build.cmd %PYTHON%\\python.exe 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
# - "build.cmd %PYTHON%\\python.exe setup.py bdist_wheel"
# - "%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.