We're getting
```No valid Python interpreter found...
# generale
echoing-manchester-70122
06/01/2020, 4:58 PMWe're getting
Copy code
No valid Python interpreter found. For this Pants version, Pants requires Python 3.6+.
Could not find . Please ensure is on your PATH. Copy code
By default, pants uses ['CPython>=2.7,<3']w
witty-crayon-22786
06/01/2020, 5:21 PMhey Adam
witty-crayon-22786
06/01/2020, 5:22 PMso, the first message is for pants itself, and the latter message is for code that pants is testing
witty-crayon-22786
06/01/2020, 5:22 PMlet me look in the release notes to answer your question
witty-crayon-22786
06/01/2020, 5:23 PMe
echoing-manchester-70122
06/01/2020, 5:26 PMis there a way to force the generated pex to use
/usr/bin/env python3w
witty-crayon-22786
06/01/2020, 5:26 PMfor which part: pants, or the code that pants is building?
e
echoing-manchester-70122
06/01/2020, 5:26 PMthe generated artifact (
pants binaryw
witty-crayon-22786
06/01/2020, 5:27 PMthat’s described here: https://www.pantsbuild.org/python_readme.html#configure-the-python-version
witty-crayon-22786
06/01/2020, 5:28 PMoh, or do you mean to set the
shebange
echoing-manchester-70122
06/01/2020, 5:28 PMyes the shebang
w
witty-crayon-22786
06/01/2020, 5:28 PMcan find-in-page in the build dictionary for “shebang”:
witty-crayon-22786
06/01/2020, 5:28 PMwitty-crayon-22786
06/01/2020, 5:29 PMshebang = ..., Use this shebang for the generated pex. (default: None)e
echoing-manchester-70122
06/01/2020, 5:29 PMthanks
6 Views