Rooba
/
peru
mirror of https://github.com/buildinspace/peru.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
peru/appveyor.yml

65 lines
2.1 KiB
YAML
Raw Normal View History

appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
# Modified from https://github.com/ogrisel/python-appveyor-demo
environment:
add run_with_env.cmd back in This is part of https://github.com/ogrisel/python-appveyor-demo, and we need it for pip to install native packages (like PyYAML). I shouldn't have removed it.
2015-12-13 15:36:41 +00:00
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 .\\appveyor\\run_with_env.cmd"
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
matrix:
- PYTHON: "C:\\Python33"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
PY_PYTHON: 3.3-32
PY_PYTHON3: 3.3-32
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
- PYTHON: "C:\\Python33-x64"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
PY_PYTHON: 3.3
PY_PYTHON3: 3.3
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
- PYTHON: "C:\\Python34"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
PY_PYTHON: 3.4-32
PY_PYTHON3: 3.4-32
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
- PYTHON: "C:\\Python34-x64"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
PY_PYTHON: 3.4
PY_PYTHON3: 3.4
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
- PYTHON: "C:\\Python35"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
PY_PYTHON: 3.5-32
PY_PYTHON3: 3.5-32
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
- PYTHON: "C:\\Python35-x64"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
PY_PYTHON: 3.5
PY_PYTHON3: 3.5
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
install:
# Prepend newly installed Python to the PATH of this build (this cannot be
# done from inside the powershell script as it would require to restart
# the parent CMD process).
- "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
# Check that we have the expected version and architecture for Python
- "python --version"
- "python -c \"import struct; print(struct.calcsize('P') * 8)\""
# Upgrade to the latest version of pip to avoid it displaying warnings
# about it being out of date.
- "pip install --disable-pip-version-check --user --upgrade pip"
# Install the build dependencies of the project. If some dependencies contain
# compiled extensions and are not provided as pre-built wheel packages,
# pip will build them from source using the MSVC compiler matching the
# target Python version and architecture
- "%CMD_IN_ENV% pip install -r requirements-dev.txt"
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
# The AppVeyor ftype for Python files is hardcoded to the Python 2
# interpreter, instead of the py.exe launcher. This works around that problem
# until a fix is in:
# http://help.appveyor.com/discussions/problems/2569-latest-appveyor-build-platform-update-introduced-a-python-problem#comment_38756340
- ps: cmd /c ftype Python.File="C:\Windows\py.exe" "%1" %*
delete the reg key that assciates VisualStudio with .py files All of our plugin tests were failing on AppVeyor, because executing .py files was popping up a "How do you want to open this type of file?" dialog and turning the script into a no-op. Deleting this reg key allows Python scripts to run with the usual interpreter.
2015-12-21 19:22:41 +00:00
clean up appveyor.yml https://github.com/oconnor663/appveyor-exec-py makes it clear that we have to set both PY_PYTHON and PY_PYTHON3 if we want to control the Python versions that plugins execute with. See also https://docs.python.org/3.3/using/windows.html. Deleting the VisualStudio reg key was a temporary workaround for an AppVeyor bug, no longer needed.
2015-12-22 06:25:41 +00:00
build: off
appveyor.yml I copied most of this from https://github.com/oconnor663/duct, which in turn copied most of it from https://github.com/ogrisel/python-appveyor-demo.
2015-11-17 00:19:47 +00:00
test_script:
run AppVeyor tests in verbose mode
2015-12-21 19:49:30 +00:00
- "%CMD_IN_ENV% python test.py -v"