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
Sometimes I find myself in a position where I want to deploy python to an environment outside system packaging, like pyenv does, but only needing a single python version. Effectively: I want to make a single python venv of a specific version, which you could imagine as part of a quick deploy&install script.
I inspected the python-build script and suspect it possible to make this work with no massive changes. Then the question becomes: is pyenv the place to implement this or should I create a separate tool that does this, building on the pyenv work and its generous licence to avoid re-implementing the build scripting?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sometimes I find myself in a position where I want to deploy python to an environment outside system packaging, like pyenv does, but only needing a single python version. Effectively: I want to make a single python venv of a specific version, which you could imagine as part of a quick deploy&install script.
I imagine it something like this:
I inspected the python-build script and suspect it possible to make this work with no massive changes. Then the question becomes: is pyenv the place to implement this or should I create a separate tool that does this, building on the pyenv work and its generous licence to avoid re-implementing the build scripting?
Beta Was this translation helpful? Give feedback.
All reactions