title: Export Conda Environment with minimized requirements
body: <p>The typical command to export a Anaconda environment to a YAML file is:</p>
  <p><code>conda env export --name my_env &gt; myenv.yml</code></p>
  <p>However, one huge issue is the readbility of this file as it includes hard specifications for all of the libraries and all of their dependencies. Is there a way for Anaconda to export a list of the optimally smallest subset of commands that would subsume these dependencies to make the YAML more readable? For example, if all you installed in a conda environment was <code>pip</code> and <code>scipy</code>, is there a way for Anaconda to realize that the file should just read:</p>
  <pre><code>name: my_env
  channels:
    - defaults
  dependencies:
    - scipy=1.3.1
    - pip=19.2.3
  </code></pre>
  <p>That way, the anaconda environment will still have the exact same specification, if not an improved on (if an upstream bug is fixed) and anyone who looks at the yml file will understand what is &quot;required&quot; to run the code, in the sense that if they did want to/couldn't use the conda environment they would know what packages they needed to install?</p>