|
| 1 | +# adapted from https://packaging.python.org/en/latest/appveyor/ |
| 2 | + |
| 3 | + |
| 4 | +environment: |
| 5 | + # we tell Tox to use "twisted[windows]", to get pypiwin32 installed |
| 6 | + #TWISTED_EXTRAS: "[windows]" |
| 7 | + # that didn't work (it seems to work when I run it locally, but on appveyor |
| 8 | + # it fails to install the pypiwin32 package). So don't bother telling |
| 9 | + # Twisted to support windows: just install it ourselves. |
| 10 | + # EXTRA_DEPENDENCY: "pypiwin32" |
| 11 | + matrix: |
| 12 | + # For Python versions available on Appveyor, see |
| 13 | + # http://www.appveyor.com/docs/installed-software#python |
| 14 | + - PYTHON: "C:\\Python27" |
| 15 | + - PYTHON: "C:\\Python27-x64" |
| 16 | + DISTUTILS_USE_SDK: "1" |
| 17 | + - PYTHON: "C:\\Python34" |
| 18 | + - PYTHON: "C:\\Python34-x64" |
| 19 | + DISTUTILS_USE_SDK: "1" |
| 20 | + - PYTHON: "C:\\Python35" |
| 21 | + - PYTHON: "C:\\Python35-x64" |
| 22 | + - PYTHON: "C:\\Python36" |
| 23 | + - PYTHON: "C:\\Python36-x64" |
| 24 | + |
| 25 | +install: |
| 26 | + - | |
| 27 | + %PYTHON%\python.exe -m pip install wheel tox |
| 28 | +
|
| 29 | +# note: |
| 30 | +# %PYTHON% has: python.exe |
| 31 | +# %PYTHON%\Scripts has: pip.exe, tox.exe (and others installed by bare pip) |
| 32 | + |
| 33 | + |
| 34 | +build: off |
| 35 | + |
| 36 | +test_script: |
| 37 | + # Put your test command here. |
| 38 | + # Note that you must use the environment variable %PYTHON% to refer to |
| 39 | + # the interpreter you're using - Appveyor does not do anything special |
| 40 | + # to put the Python evrsion you want to use on PATH. |
| 41 | + - | |
| 42 | + misc\windows-build.cmd %PYTHON%\Scripts\tox.exe -e py |
| 43 | +
|
| 44 | +after_test: |
| 45 | + # This step builds your wheels. |
| 46 | + # Again, you only need build.cmd if you're building C extensions for |
| 47 | + # 64-bit Python 3.3/3.4. And you need to use %PYTHON% to get the correct |
| 48 | + # interpreter |
| 49 | + - | |
| 50 | + misc\windows-build.cmd %PYTHON%\python.exe setup.py bdist_wheel |
| 51 | +
|
| 52 | +artifacts: |
| 53 | + # bdist_wheel puts your built wheel in the dist directory |
| 54 | + - path: dist\* |
| 55 | + |
| 56 | +#on_success: |
| 57 | +# You can use this step to upload your artifacts to a public website. |
| 58 | +# See Appveyor's documentation for more details. Or you can simply |
| 59 | +# access your wheels from the Appveyor "artifacts" tab for your build. |
0 commit comments