You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
Hmmm... it was passing the CI earlier. Do you have the failure on-hand? I agree about being explicit, but IMO we should explicitly use python3. My team and I have had issues running this locally with python2 versions of virtualenv and cairo. @yiyix: You were unable to build with python2, correct?
The reason will be displayed to describe this comment to others. Learn more.
I don't have the failure; it's hard to find when commits are rewritten :/
I don't really mind this requiring Python 3 since it isn't run that often, but in general the project currently requires Python 2 and some parts have experimental support for Python 3. So it would be a substantive change to make, and probably deserves wider review (probably qualifies for an RFC).
The reason will be displayed to describe this comment to others. Learn more.
I was unable to build it with python 3.
This line virtualenv -p python .virtualenv allows the system to use the which ever python version available in /usr/local/bin/python. So the build file works with both python2 and python 3.
I agree that this change needs a wider review, I will submit a separate review request.
6a53164
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.
Why is this necessary? I've been running it in python3 without issue.
6a53164
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.
#23357
6a53164
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 assume that it failed CI without this change, but I don't remember the details.
In any case we shouldn't say
python
and expect py3 to be used, and we should be specific and consistent about which version we're using for this.6a53164
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.
Hmmm... it was passing the CI earlier. Do you have the failure on-hand? I agree about being explicit, but IMO we should explicitly use python3. My team and I have had issues running this locally with python2 versions of virtualenv and cairo.
@yiyix: You were unable to build with python2, correct?
6a53164
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 don't have the failure; it's hard to find when commits are rewritten :/
I don't really mind this requiring Python 3 since it isn't run that often, but in general the project currently requires Python 2 and some parts have experimental support for Python 3. So it would be a substantive change to make, and probably deserves wider review (probably qualifies for an RFC).
6a53164
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 was unable to build it with python 3.
This line virtualenv -p python .virtualenv allows the system to use the which ever python version available in /usr/local/bin/python. So the build file works with both python2 and python 3.
I agree that this change needs a wider review, I will submit a separate review request.