title: Using virtualenvwrapper and pyenv together
body: <p><code>$ pyenv virtualenv 3.8.0 tf12</code> creates a virtualenv located in <code>~/.pyenv/versions/3.8.0/envs/tf12</code> which contains packages we installed into it using <code>pip install</code>.  If we create a new project directory like <code>mkdir myfolder &amp;&amp; cd myfolder &amp;&amp; pyenv local tf12</code>, that project directory will use the same kernels and packages that the tf12 environment contains because we used the <code>pyenv local</code> command.</p>
  <p>But then we also have virtualenvs and directories created with <code>mkproject mynewenv</code> located somewhere like <code>~/.ve</code> and <code>~/workspace</code>. The workspace is where we place notebooks, code and scripts <code>.pynb</code>, <code>.py</code>, <code>.r</code> etc and the corresponding virtualenv uses the global python version that was active when executing <code>mkproject mynewenv</code>.</p>
  <p>These virtualenvs created with <code>mkproject mynewenv</code> are separate from virtualenvs created with <code>pyenv virtualenv</code>.</p>
  <p>I have come to the conclusion that we cannot use them together for further possibilities. They are used independently. Correct me if I'm wrong.</p>