##// END OF EJS Templates
Predict the Python version based on $VIRTUAL_ENV...
Predict the Python version based on $VIRTUAL_ENV Try to make prediction of the Python's site-package version used by virtualenv. If predicted path doesn't exist, continue with previous behaviour. This can be useful while working with different Python versions in virtual environments other than system-used (previously provided via `sys.version_info`). Note that this *only* updates $PYTHONPATH, so 3rd-libraries installed in virtualenv will be avialable. However the Python interpreter contiunues to be other than the bundled in the virtualenv (see `init_virtualenv()` docstring).

File last commit:

r26183:61376395
r26257:2704824e
Show More
appveyor.yml
31 lines | 772 B | text/x-yaml | YamlLexer
build: false
matrix:
fast_finish: true # immediately finish build once one of the jobs fails.
environment:
matrix:
- PYTHON: "C:\\Python37-x64"
PYTHON_VERSION: "3.7.x"
PYTHON_ARCH: "64"
- PYTHON: "C:\\Python38"
PYTHON_VERSION: "3.8.x"
PYTHON_ARCH: "32"
- PYTHON: "C:\\Python38-x64"
PYTHON_VERSION: "3.8.x"
PYTHON_ARCH: "64"
init:
- "ECHO %PYTHON% %PYTHON_VERSION% %PYTHON_ARCH%"
install:
- "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
- "%CMD_IN_ENV% python -m pip install --upgrade setuptools pip"
- "%CMD_IN_ENV% pip install nose coverage pytest"
- "%CMD_IN_ENV% pip install .[test]"
- "%CMD_IN_ENV% mkdir results"
- "%CMD_IN_ENV% cd results"
test_script:
- "%CMD_IN_ENV% iptest --coverage xml"