Merge branch 'master' into feature/update-pip-piptools

This commit is contained in:
Dan Ryan
2020-04-28 15:24:43 -04:00
committed by GitHub
3 changed files with 11 additions and 9 deletions
+2
View File
@@ -6,7 +6,9 @@ Pipenv: Python Development Workflow for Humans
[![Azure Pipelines Build Status](https://dev.azure.com/pypa/pipenv/_apis/build/status/Pipenv%20CI?branchName=master)](https://dev.azure.com/pypa/pipenv/_build/latest?definitionId=16&branchName=master)
[![image](https://img.shields.io/pypi/pyversions/pipenv.svg)](https://python.org/pypi/pipenv)
------------------------------------------------------------------------
[[ ~ Dependency Scanning by PyUp.io ~ ]](https://pyup.io)
**Pipenv** is a tool that aims to bring the best of all packaging worlds
(bundler, composer, npm, cargo, yarn, etc.) to the Python world.
+8 -9
View File
@@ -237,16 +237,15 @@ Example::
.. note::
In order to enable this functionality while maintaining its permissive
copyright license, `pipenv` embeds an API client key for the backend
Safety API operated by pyup.io rather than including a full copy of the
CC-BY-NC-SA licensed Safety-DB database. This embedded client key is
shared across all `pipenv check` users, and hence will be subject to
API access throttling based on overall usage rather than individual
client usage.
Each month, `PyUp.io` updates the ``safety`` database of
insecure Python packages and `makes it available to the
community for free <https://pyup.io/safety/>`__. Pipenv
makes an API call to retrieve those results and use them
each time you run ``pipenv check`` to show you vulnerable
dependencies.
You can also use your own safety API key by setting the
environment variable ``PIPENV_PYUP_API_KEY``.
For more up-to-date vulnerability data, you may also use your own safety
API key by setting the environment variable ``PIPENV_PYUP_API_KEY``.
☤ Community Integrations
+1
View File
@@ -0,0 +1 @@
Updated PyUp.io information to reflect current situation.