forked from Blosc/bcolz
-
Notifications
You must be signed in to change notification settings - Fork 0
/
appveyor.yml
86 lines (73 loc) · 2.45 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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
environment:
global:
# SDK v7.0 MSVC Express 2008's SetEnv.cmd script will fail if the
# /E:ON and /V:ON options are not enabled in the batch script intepreter
# See: http://stackoverflow.com/a/13751649/163740
CMD_IN_ENV: "cmd /E:ON /V:ON /C .\\continuous-integration\\appveyor\\run_with_env.cmd"
matrix:
# PYTHON 2.6
- PYTHON: "C:\\Python26_32"
PYTHON_VERSION: "2.6"
PYTHON_ARCH: "32"
CONDA_PY: "26"
CONDA_NPY: "111"
# - PYTHON: "C:\\Python26_64"
# PYTHON_VERSION: "2.6"
# PYTHON_ARCH: "64"
# CONDA_PY: "26"
# CONDA_NPY: "111"
# PYTHON 2.7
- PYTHON: "C:\\Python27_32"
PYTHON_VERSION: "2.7"
PYTHON_ARCH: "32"
CONDA_PY: "27"
CONDA_NPY: "111"
# - PYTHON: "C:\\Python27_64"
# PYTHON_VERSION: "2.7"
# PYTHON_ARCH: "64"
# CONDA_PY: "27"
# CONDA_NPY: "111"
# PYTHON 3.4
- PYTHON: "C:\\Python34_32"
PYTHON_VERSION: "3.4"
PYTHON_ARCH: "32"
CONDA_PY: "34"
CONDA_NPY: "111"
# This does not work and I am still wondering why? why? why?
#- PYTHON: "C:\\Python34_64"
# PYTHON_VERSION: "3.4"
# PYTHON_ARCH: "64"
# DISTUTILS_USE_SDK: "1"
# CONDA_PY: "34"
# CONDA_NPY: "19"
# PYTHON 3.5
- PYTHON: "C:\\Python35_32"
PYTHON_VERSION: "3.5"
PYTHON_ARCH: "32"
CONDA_PY: "35"
CONDA_NPY: "111"
- PYTHON: "C:\\Python35_64"
PYTHON_VERSION: "3.5"
PYTHON_ARCH: "64"
CONDA_PY: "35"
CONDA_NPY: "111"
install:
# this installs the appropriate Miniconda (Py2/Py3, 32/64 bit),
# as well as pip, conda-build, and the binstar CLI
- powershell .\\continuous-integration\\appveyor\\install.ps1
- "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
build: false
test_script:
# Build and test the package. This appears(?) to sporadically fail due to a
# bug in conda-build on 32 bit python.
# https://github.com/conda/conda-build/issues/152
#
# Note also that our setup.py script, which is called by conda-build, writes
# a __conda_version__.txt file, so the version number on the binary package
# is set dynamically. This unfortunately mean that conda build --output
# doesn't really work.
#
- "%CMD_IN_ENV% conda install --yes --quiet cython pandas mock"
# Build the compiled extension and run the project tests
- "%CMD_IN_ENV% python setup.py build_ext --inplace"
- "%CMD_IN_ENV% python -c \"import bcolz; bcolz.test(heavy=True)\""