kennethreitz/pipenv
1
0
Fork 0
mirror of https://github.com/kennethreitz/pipenv.git synced 2026-06-05 22:50:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revise pipenv check caveat for pyup.io feedback

Browse Source 
Jannis Gebauer of pyup.io let us know that he's definitely fine
with commercial *use* of the `pipenv check` feature, so it's
only commercial redistributors of `pipenv` that may need to
take a closer look at the licensing situation, and perhaps
talk to `pyup.io` directly.

Follow-up to #1651
This commit is contained in:
Nick Coghlan
2018-03-14 21:06:13 +10:00
committed by GitHub
parent 9a87a9a3f3
commit c1947126dc
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/advanced.rst
+6 -5
View File
@@ -186,11 +186,12 @@ Example::
.. note::
Commercial users and redistributors of `pipenv` should be aware that the public
`Safety-DB` project backing this feature is licensed as CC-BY-NC-SA. Non-commercial
use of this feature and use by organisations with their own pyup.io commercial license
are thus both clearly fine, but other commercial redistributors and end users may want
to perform their own legal assessment before relying on the capability.
Commercial redistributors of `pipenv` should be aware that the public `Safety-DB`
project backing this feature is licensed as CC-BY-NC-SA by `pyup.io`. While
`pyup.io` have [stated explicitly](https://github.com/pypa/pipenv/issues/1651#issuecomment-372583779)
that commercial *use* of this `pipenv` feature is fine, commercial redistributors may want
to perform their own legal assessment and perhaps chat directly to `pyup.io` about
the specific licensing terms.
☤ Community Integrations