[Tutor] how to install python3.8 using virtualenvwrapper

[Alex Kleider]

On 2020-05-09 18:18, Don Jennings wrote:
> I’m glad you were able to make progress.
> 
> I’ve been using pyenv [1] ever since I read a piece by Jacob
> Kaplan-Moss about his choice of tools [2]. Recently I replaced pipenv
> with pyenv-virtualenv [3] and direnv [4] to the mix. It’s the best
> setup I’ve ever used for managing multiple projects with differing
> requirements. I’d be remiss if I didn’t mention pipx [5] for python
> command line tools like black, flake8 and awscli.
> 
> Best,
> Don
> 
> [1] https://github.com/pyenv/pyenv
> [2] https://jacobian.org/2018/feb/21/python-environment-2018/
> [3] https://github.com/pyenv/pyenv-virtualenv
> [4] https://direnv.net
> [5] https://github.com/pipxproject/pipx
> 
So many choices.
I notice there is an update to your reference [2]:
https://jacobian.org/2019/nov/11/python-environment-2020/
It also seems that your system allows you to bring in any version of 
python without compiling locally.

My impression (rightly or wrongly) is that for virtualenv (and 
virtualenvwrapper) there's a file system with all python related code 
for each venv while with the system(s) you describe, there's only one 
copy of each version of Python and the venv 'knows' which one to use 
thus saving disk space.  That would be a considerable advantage if you 
had many venvs using the same Python version but different in other 
respects (imported modules.)

Thanks for your note.
Alex