anchor.diff:  
   This buildpack will be automatically used if there is a `requirements.txt` or `setup.py` file in the root directory of your project.
   
  -If your Cloud Foundry deployment does not have the Python Buildpack installed, or the installed version is out of date, you can use the latest version with the command:
  +If your Cloud Foundry deployment does not have the Python Buildpack installed, or the installed version is out of date, you can use the latest version by specifying it with the `-b` option when you push your app. For example:
   
   <pre class="terminal">
   $ cf push my_app -b https://github.com/cloudfoundry/buildpack-python.git
  
positive.code: 
  ## <a id='supported_versions'></a>Supported Versions ##
  
  Supported Python versions can be found [in the release notes](https://github.com/cloudfoundry/python-buildpack/releases).
  
  ## <a id='runtime'></a>Specify a Python Version ##
  
  Specific versions of the Python runtime can be specified with a `runtime.txt` file:
  
  <pre class="terminal">
  $ cat runtime.txt
  python-3.5.2
  </pre>
  
  The buildpack only supports the stable Python versions, which are listed in the `manifest.yml` and [releases page](https://github.com/cloudfoundry/python-buildpack/releases).
  
  If you try to use a binary that is not currently supported, staging your app will fail and you will see the following error message:
  
  <pre class="terminal">
  Could not get translated url, exited with: DEPENDENCY_MISSING_IN_MANIFEST: ...
  
negative.code: ## <a id='proxy_support'></a> Proxy Support ##
  
  If you need to use a proxy to download dependencies during staging, you can set
  the `http_proxy` and `https_proxy` environment variables. For more information, see the [Proxy Usage Documentation](http://docs.cloudfoundry.org/buildpacks/proxy-usage.html).
  
  ## <a id='bosh_trusted_cert'></a>BOSH Configured Custom Trusted Certificate Support ##
  
  