Pyenv – Python Runtime Version Manager – to install, uninstall, list or switch between different python runtimes
Pipenv – Python Package Manager and Virtual environment manager – to create an isolated virtual environment with a specific python runtime – to install, uninstall, list python packages
Venv – Virtual environment manager (for Python 3) – to create an isolated virtual environment with a specific python runtime – python packages will be isolated already
Virtualenv – Virtual environment manager (for Python 2) – to create an isolated virtual environment with a specific python runtime – python packages will be isolated already
Installing Python Runtime Versions via Pyenv
In order to test different Python Runtime versions, I have installed some versions.
$ pyenv install 3.10.2
$ pyenv install 3.10.3
$ pyenv install 3.10.4
$ pyenv install 3.10.5
I have 4 Python runtime versions(3.10.2, 3.10.3, 3.10.4, 3.10.5) in my machine. So, let's list them.
$ pyenv versions
system
3.10.2
3.10.3
3.10.4
* 3.10.5 (set by /Users/kenanhancer/.pyenv/version)
When we want to check whether current terminal is attached to stdin, stdout and stderr streams or not, we can use the below codes. I tried with piping, and redirection so both works well.
As seen in below 6 usages, stdin is not listed in output of commands except first one. Because stdin is used by piping or redirection.
In a pipeline, template expression variables (${{ variables.var }}) get processed at compile time, before runtime starts. Macro syntax variables ($(var)) get processed during runtime before a task runs. Runtime expressions ($[variables.var]) also get processed during runtime but are intended to be used with conditionsand expressions.