title: conda list vs pip list differences in conda created environment
body: <p>I am using conda version 4.5.11, python 3.6.6, and Windows 10.</p>
  
  <p>I create a virtual environment using conda</p>
  
  <pre><code>conda create --name venv
  </code></pre>
  
  <p>When I check for installed packages</p>
  
  <pre><code>conda list
  </code></pre>
  
  <p>it is (as expected), empty.</p>
  
  <p>But</p>
  
  <pre><code>pip list
  </code></pre>
  
  <p>is quite long.</p>
  
  <p>Question #1: Why? - when I create a virtual environment using</p>
  
  <pre><code>python -m venv venv
  </code></pre>
  
  <p>the pip list is empty.</p>
  
  <p>When I am not in an activated virtual environment, then</p>
  
  <pre><code>conda list
  </code></pre>
  
  <p>is also quite long, but it isn't the same as the pip list (* see follow up below)
  In general, the pip list is a subset of the conda list. There is at least one exception ('tables' in the pip list, not in conda list) but I haven't analysed too closely. The conda list changes/displays some (all?) hyphens to underscores (or pip does the reverse). There also a few instances of versions being different.</p>
  
  <p>Question #2: Why? (and follow up questions - can they be? and should I care?)</p>
  
  <p>I was hoping to have a baseline conda 'environment' (that may not be the right word) -ie, the packages I have installed/updated into Ananconda/conda and then all virtual environments would be pulled from that. If I needed to install something new, it would be first installed into the baseline. Only when I need to create an application using different versions of packages from the baseline (which I don't envision in the foreseeable future) would I need to update the virtual environments differently.</p>
  
  <p>Question #3: Am I overthinking this? I am looking for consistency and hoping for understanding.</p>
  
  <p>-- Thanks. 
  Craig</p>
  
  <p>Follow Up #1: After installing some packages to my empty conda venv, the results of conda list and pip list are still different, but the pip list is much shorter than it was, but is a subset of the conda list (it does not include two packages I don't use, so I don't care)</p>
  
  <p>Follow Up #2: In the empty environment, I ran some code</p>
  
  <pre><code>python my-app.py
  </code></pre>
  
  <p>and was only mildly surprised that it ran without errors. As expected, when I installed a package (pytest), it failed to run due to the missing dependencies. So ... empty is not empty.</p>