|
| 1 | +environment: |
| 2 | + |
| 3 | + matrix: |
| 4 | + |
| 5 | + # For Python versions available on Appveyor, see |
| 6 | + # http://www.appveyor.com/docs/installed-software#python |
| 7 | + # The list here is complete (excluding Python 2.6, which |
| 8 | + # isn't covered by this document) at the time of writing. |
| 9 | + |
| 10 | + - PYTHON: "C:\\Python27" |
| 11 | + - PYTHON: "C:\\Python34" |
| 12 | + - PYTHON: "C:\\Python35" |
| 13 | + - PYTHON: "C:\\Python27-x64" |
| 14 | + - PYTHON: "C:\\Python34-x64" |
| 15 | + DISTUTILS_USE_SDK: "1" |
| 16 | + |
| 17 | + # Python35-x64 test fails with MemoryError |
| 18 | + # TODO: investigate it |
| 19 | + #- PYTHON: "C:\\Python35-x64" |
| 20 | + |
| 21 | +install: |
| 22 | + # We need wheel installed to build wheels |
| 23 | + - "%PYTHON%\\python.exe -m pip install -U pip wheel pytest cython" |
| 24 | + |
| 25 | +build: off |
| 26 | + |
| 27 | +test_script: |
| 28 | + # Put your test command here. |
| 29 | + # If you don't need to build C extensions on 64-bit Python 3.3 or 3.4, |
| 30 | + # you can remove "build.cmd" from the front of the command, as it's |
| 31 | + # only needed to support those cases. |
| 32 | + # Note that you must use the environment variable %PYTHON% to refer to |
| 33 | + # the interpreter you're using - Appveyor does not do anything special |
| 34 | + # to put the Python evrsion you want to use on PATH. |
| 35 | + - "build.cmd %PYTHON%\\python.exe setup.py build_ext -i" |
| 36 | + - "build.cmd %PYTHON%\\python.exe setup.py install" |
| 37 | + - "%PYTHON%\\python.exe -c \"import sys; print(hex(sys.maxsize))\"" |
| 38 | + - "%PYTHON%\\python.exe -c \"from msgpack import _packer, _unpacker\"" |
| 39 | + - "%PYTHON%\\Scripts\\py.test test" |
| 40 | + - "build.cmd %PYTHON%\\python.exe setup.py bdist_wheel" |
| 41 | + |
| 42 | +after_test: |
| 43 | + # This step builds your wheels. |
| 44 | + # Again, you only need build.cmd if you're building C extensions for |
| 45 | + # 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct |
| 46 | + # interpreter |
| 47 | + |
| 48 | +artifacts: |
| 49 | + # bdist_wheel puts your built wheel in the dist directory |
| 50 | + - path: dist\* |
| 51 | + |
| 52 | +#on_success: |
| 53 | +# You can use this step to upload your artifacts to a public website. |
| 54 | +# See Appveyor's documentation for more details. Or you can simply |
| 55 | +# access your wheels from the Appveyor "artifacts" tab for your build. |
| 56 | + |
| 57 | +# vim: set shiftwidth=2 |
0 commit comments