You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+39-7Lines changed: 39 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,16 @@
2
2
3
3
The Python third_party_license_file_generator is aimed at distilling down the appropriate license for one or many pip "requirements" files into a single file; it supports Python2.7 and Python3.
4
4
5
+
## Thanks to everyone who has contributed over the years!
@@ -16,12 +26,12 @@ With no arguments (other than a pip "requirements" file and a Python executable
16
26
17
27
- walk the given Python executable's site-packages folder and build up package metadata (and license files, if present)
18
28
- filter down by packages that are listed in the pip "requirements" file (and those packages dependencies, and their dependencies, and their dependencies... you get the gist)
19
-
- note: it follows "-r some_file.txt" references found in the pip "requirements" files
29
+
- note: it follows "-r some_file.txt" references found in the pip "requirements" files
20
30
- if a license name could not be secured for a package, try to gather that from the package's PyPI web page
21
-
- if a license name has still not been secured and the package lists a GitHub home page, try to find a license from there
22
-
- otherwise, assume the package to be commercially licensed (as it is legally understood that is the case)
31
+
- if a license name has still not been secured and the package lists a GitHub home page, try to find a license from there
32
+
- otherwise, assume the package to be commercially licensed (as it is legally understood that is the case)
23
33
- if a license file could not be secured for a package and the package lists a GitHub home page, try to find a license from there
24
-
- otherwise, create a license (for the known license name) from a local collection of licenses (within the Python Third Party License Generator)
34
+
- otherwise, create a license (for the known license name) from a local collection of licenses (within the Python Third Party License Generator)
25
35
- show a summary of packages against licenses to the user
26
36
- build a THIRDPARTYLICENSES file in the current folder
27
37
- give a return code of zero for success or non-zero for failures (e.g. GPL-licensed packages detected when specified to not permit GPL)
@@ -62,13 +72,13 @@ Three different pip "requirements" files, two different Python paths (need to re
62
72
-p ~/.virtualenvs/api_pypy/bin/python \
63
73
-r cpython_requirements.txt \
64
74
-p ~/.virtualenvs/api_py/bin/python \
65
-
-x uWSGI \
75
+
-x uWSGI \
66
76
-o ThirdPartyLicenses.txt
67
77
68
78
Three different pip "requirements" files, two different Python paths (need to repeat), a GPL exception, a custom output file and a license override file:
description='The Python third_party_license_file_generator is aimed at distilling down the appropriate license for one or many pip "requirements" files into a single file; it supports Python2.7 and Python3.',
27
45
long_description=long_description,
28
46
long_description_content_type="text/markdown",
@@ -62,10 +80,17 @@
62
80
# your project is installed. For an analysis of "install_requires" vs pip's
0 commit comments