title: Can a virtualenv created on Windows be used from WSL bash?
body: <p>I'm using Windows Subsystem for Linux (WSL) for a test project (obeythetestinggoat) and had a ton of issues trying to get virtualenv to work from the shell or CMD to ensure I was using the latest Python version installed (3.6).  </p>
  
  <pre><code>mkvirtualenv --python="C:\Program Files\Python36\python.exe" superlists
  </code></pre>
  
  <p>I can get both bash and CMD running the virtualenv, but both report different versions of Python.<br>
  CMD:</p>
  
  <pre><code>python -V
  Python 3.6.0
  </code></pre>
  
  <p>Bash:</p>
  
  <pre><code>python -V
  Python 2.7.6
  
  python3 -V
  Python 3.4.3
  </code></pre>
  
  <p>Since the venv was created with the CMD shell, I would think it would control the version used, and the Scripts folder shows python36.dll, so assume it should be 3.6.  </p>
  
  <p>So it seems like the Bash WSL environment is controlling what version is used, regardless of any ENV paths I set.  I think I might ditch the Windows approach and go use my Ubuntu install, but really want to understand what is happening here, especially in regards to the virtualenv as it seems to negate the purpose of it all if the shell is only using what came with it and will not use the version supposedly in the virtual env.  Any help would be appreciated!</p>