title: Migrating from virtualenv to venv
body: <p>I am/was a happy user of <code>virtualenv</code> for years. Switched to <code>Python 3</code> for all my projects a year a ago. <code>Python 3</code> has a command line switch to create/manage virtual environments like so: </p>
  
  <p><code>python3 venv my_virtualenv</code></p>
  
  <p>After reading this article <a href="https://medium.com/@henriquebastos/the-definitive-guide-to-setup-my-python-workspace-628d68552e14" rel="nofollow noreferrer">The definitive guide to setup my Python workspace</a>, I would like to use <code>pyenv</code> to manage different installations of Python 3.x on my Mac in combination with <code>venv</code>.</p>
  
  <p>From this article [1] I get that <code>pyenv-virtualenv</code> needs/uses <code>venv</code>. </p>
  
  <p>I have a ton of virtual environments created in the past years with <code>virtualenv</code> in <code>$HOME/.virtualenvs</code>. Is there a way to "migrate" those virtual environments to <code>venv</code>? Or is there a way to define a <code>WORKON_HOME</code> folder for <code>venv</code>? I use/d this for <code>virtualenv</code> in my zsh config file:</p>
  
  <p><code>export WORKON_HOME=$HOME/.virtualenvs</code></p>
  
  <hr>
  
  <p>[1] <a href="https://stackoverflow.com/questions/41573587/what-is-the-difference-between-venv-pyvenv-pyenv-virtualenv-virtualenvwrappe">What is the difference between venv, pyvenv, pyenv, virtualenv, virtualenvwrapper, pipenv, etc?</a> </p>