Skip to content

Conversation

@targos
Copy link
Member

@targos targos commented Oct 31, 2019

Tested on Windows.

/cc @nodejs/python @cclauss

@targos targos added build Issues and PRs related to build files or the CI. python PRs and issues that require attention from people who are familiar with Python. labels Oct 31, 2019
@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Oct 31, 2019
@nodejs-github-bot
Copy link
Collaborator

# pyenv will alert which shims are available and then will fail the build.
_=[ 'exec' '/bin/sh' '-c' '''
test ${TRAVIS} && exec python "$0" "$@" # workaround for pyenv on Travis CI
which python3.8 >/dev/null && exec python3.8 "$0" "$@"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we maybe check for python3 first?

Copy link
Contributor

@cclauss cclauss Oct 31, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The trouble with doing that is that python3 might be in ((3, 0), (3, 1), (3, 2), (3, 3), (3, 4)) which we (and the Python Core Team) do not support.

@sam-github
Copy link
Contributor

I'm fine with this, but I wonder if we should be so specific, can't we just say 3.5 and above?

@cclauss
Copy link
Contributor

cclauss commented Oct 31, 2019

Explicit is better than implicit is line 2 of The Zen of Python written in 2004.
I do believe that we should prefer the most current supported Python that which can find.

@cclauss
Copy link
Contributor

cclauss commented Nov 2, 2019

Landed in 3a076ba

@cclauss cclauss closed this Nov 2, 2019
cclauss pushed a commit that referenced this pull request Nov 2, 2019
PR-URL: #30194
Reviewed-By: Christian Clauss <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: David Carlier <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
@targos targos deleted the py3.8 branch November 2, 2019 14:32
targos added a commit that referenced this pull request Nov 5, 2019
PR-URL: #30194
Reviewed-By: Christian Clauss <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: David Carlier <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jiawen Geng <[email protected]>
@targos targos mentioned this pull request Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. python PRs and issues that require attention from people who are familiar with Python.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants