In some places, I had forgotten to use ${PYTHONEXEC}, and used python.
Changes made:
Basically s/python/${PYTHONEXEC}/g
Related issues:
67
Additional information:
Eventhough we call ${PYTHONEXEC} everywhere, the issue is that the python code imports packages that do not exist in the standard library for python2.7, namely secrets.
Maybe they can be imported manually before running the bootstrap.
The use of ${PYTHONEXEC} was to allow the bootstrap to point to another python3 location, not to make it python2.7-compatible. (We won't support the latter).
Describe the pull request:
Pull request long description:
In some places, I had forgotten to use
${PYTHONEXEC}, and usedpython.Changes made:
Basically
s/python/${PYTHONEXEC}/gRelated issues:
67
Additional information:
Eventhough we call
${PYTHONEXEC}everywhere, the issue is that the python code imports packages that do not exist in the standard library forpython2.7, namelysecrets. Maybe they can be imported manually before running the bootstrap.The use of
${PYTHONEXEC}was to allow the bootstrap to point to another python3 location, not to make itpython2.7-compatible. (We won't support the latter).