anchor.diff:  
   - Specify a start command in the application manifest by setting the `command` attribute. For more information, see the [Deploying with Application Manifests](../../devguide/deploy-apps/manifest.html#start-commands) topic. 
   
  -## <a id='vendoring'></a>Vendor App Dependencies ##
  +
  +## <a id='vendoring'></a> Vendor App Dependencies
   
   If you are deploying in an environment that is disconnected from the Internet, your application [must vendor its dependencies](https://github.com/cf-buildpacks/buildpack-packager/blob/master/doc/disconnected_environments.md).
   
  
positive.code: Staging failed: Buildpack compilation step failed
  </pre>
  
  ## <a id='start-command'></a>Specify a Start Command ##
  
  The Python buildpack does not generate a [default start command](../../devguide/deploy-apps/start-restart-restage.html#first-time) for your applications.
  
  
negative.code: 
  <p class="note"><strong>Note</strong>: To ensure proper installation of dependencies, we recommend non-binary vendored dependencies. The above <code>pip install</code> command achieves this.</p>
  
  
  ## <a id='cfenv'></a> Parse Environment Variables
  
  The `cfenv` package provides access to Cloud Foundry application environment settings by parsing all the relevant environment variables. The settings are returned as a class instance. See [https://github.com/jmcarp/py-cfenv](https://github.com/jmcarp/py-cfenv) for more information.
  
  
  ## <a id='miniconda'></a> Miniconda Support <span style="font-size:1rem">(starting in buildpack version <a href="https://github.com/cloudfoundry/python-buildpack/releases/tag/v1.5.6">1.5.6</a>)</span>
  
  To use miniconda instead of pip for installing dependencies, place an `environment.yml` file in the root directory.
  
  