setuptools license information suggests that setuptools only contains code under MIT license. However that is incorrect. Setuptools vendors and ships code that has different licenses
- Since commit 00384a5 and 71.0.0, setuptools has been vendoring the
autocommand package. The autocommand package has the copyleft license LGPLv3
- importlib_metadata, importlib_resources, and packaging are under Apache Software License. packaging is also under BSD license
- typing_extesion is under Python Software Foundation License
Please make sure that setuptools correctly declares all licenses of code that is bundled and shipped with setuptools.
I'm a bit concerned that setuptools started to include LGPL software without declaring it. LGPL code is also problematic in closed source and proprietary software. Does Python import count as static or dynamic linking?
setuptools license information suggests that setuptools only contains code under MIT license. However that is incorrect. Setuptools vendors and ships code that has different licenses
autocommandpackage. The autocommand package has the copyleft license LGPLv3Please make sure that setuptools correctly declares all licenses of code that is bundled and shipped with setuptools.
I'm a bit concerned that setuptools started to include LGPL software without declaring it. LGPL code is also problematic in closed source and proprietary software. Does Python
importcount as static or dynamic linking?