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
After experimenting a bit with adding Python versions on Travel, it probably should be tweaked a bit, mainly because it forces you to always have that version of Python in the system, which can be somewhat limiting (e.g., we need a specific image, say in a step of a Bitbucket pipeline, but it doesn't have the right Python version)
I suggest using python-build, a Pyenv plugin that takes care of the whole installation procedure. As you can see from the README, it does not need Pyenv to be installed, but can operate standalone like this:
python-build <python-version><output-directory>
where <python-version> is the version of Python to install (e.g., 3.7.15) and <output-directory> is where to install it.
It should be quite easy (maybe with Git submodules?) to go and reference Pyenv's plugin directly, so you can keep it up to date, and at the same time change the Travel command to add Python versions to something like:
After experimenting a bit with adding Python versions on Travel, it probably should be tweaked a bit, mainly because it forces you to always have that version of Python in the system, which can be somewhat limiting (e.g., we need a specific image, say in a step of a Bitbucket pipeline, but it doesn't have the right Python version)
I suggest using
python-build
, a Pyenv plugin that takes care of the whole installation procedure. As you can see from the README, it does not need Pyenv to be installed, but can operate standalone like this:where
<python-version>
is the version of Python to install (e.g., 3.7.15) and<output-directory>
is where to install it.It should be quite easy (maybe with Git submodules?) to go and reference Pyenv's plugin directly, so you can keep it up to date, and at the same time change the Travel command to add Python versions to something like:
travel config add python <python-version> [<python-location>]
python-location
available?FileNotFoundError
<python-version>
, raise aValueError
python-build
on that version to download the binary to some known internal pathconfig.yml
N.B.: The above flow chart works only on UNIX-like systems. For Windows systems, we should look for an equivalent standalone plugin in Pyenv-win.
The text was updated successfully, but these errors were encountered: