-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: appveyor windows job - python version #1776
Conversation
Why is this change necessary? * With release v0.41.0 - MSIs have version 3.7.6 as their base version. Appveyor testing needs to reflect that. How does it address the issue? * Appveyor test frameworks are now using python 3.7.6. The environment variables are set according to: https://www.appveyor.com/docs/windows-images-software/ What side effects does this change have? * None
12b6e6f
to
5c1f949
Compare
appveyor-windows.yml
Outdated
PYTHON_HOME: "C:\\Python37-x64" | ||
PYTHON_SCRIPTS: "C:\\Python37-x64\\Scripts" | ||
PYTHON_EXE: "C:\\Python37-x64\\python.exe" | ||
PYTHON_VERSION: '3.7.5' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is only for linux? Do we need this? Looks unused in the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It still adds visibility when looking at a appveyor test run.
Don't we need to update all the windows build projects as well? |
a085de0
to
393ebc4
Compare
- It does not look to be used.
Why is this change necessary?
Appveyor testing needs to reflect that.
How does it address the issue?
variables are set according to: https://www.appveyor.com/docs/windows-images-software/
What side effects does this change have?
Checklist:
make pr
passesBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.