Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@monojenkins
Copy link
Contributor

@monojenkins monojenkins commented Apr 2, 2020

Extracted from #18284

Backport of #18285 and #18197.

/cc @lewurm @NattyNarwhal

Fix locating Python interpreter when it isn't "python"

The "python" interpreter is specified by PEP-394. In it, an OS
can decide not to ship a "python" executable, and instead only
ship python2/3, providing some ambiguity for scripts that are
version-neutral, like the one Mono uses.

This uses an automake macro to locate a suitable Python, and
changes the makefile to use the located Python, whatever it may be.

(cherry picked from commit 84221f0)
I fear this causing packaging problems, but as-is we require Python 3 for most of our Python files but don't actually check for that in configure. We should be consistent about this. Some projects (notably wasm) also use the Python version detected here, so bumping this will also bump the version used in those cases (a good thing, since there are some known bugs when using the scripts with Python 2).

(cherry picked from commit 0f47ea5)
@lewurm
Copy link
Contributor

lewurm commented Apr 2, 2020

Windows x64 Android SDK lane looks good: https://jenkins.mono-project.com/job/xa/7502/

@akoeplinger
Copy link
Member

@monojenkins build failed

@akoeplinger
Copy link
Member

@monojenkins build

@akoeplinger akoeplinger merged commit 8199a27 into mono:2019-12 Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants