We use a process that looks through all of our installed Python package dependencies and collects license files for each. When a distribution package does not include its license file, that creates extra manual work for every release, making sure we have the correct license file for the version of the package that we are using.
I request that, for future releases, the license file be included in the distribution.
Since the license text is embedded in the README, including the README would be sufficient for my purposes, but others might employ processes that can only identify a license file if it has "LICENSE" in its name.
Thanks. :)
We use a process that looks through all of our installed Python package dependencies and collects license files for each. When a distribution package does not include its license file, that creates extra manual work for every release, making sure we have the correct license file for the version of the package that we are using.
I request that, for future releases, the license file be included in the distribution.
Since the license text is embedded in the README, including the README would be sufficient for my purposes, but others might employ processes that can only identify a license file if it has "LICENSE" in its name.
Thanks. :)