Replies: 3 comments 6 replies
-
Maybe it's a good idea to make it work without it, but I'm not sure what the issue is with a LGPL library or how that makes it "not FOSS-compatible" (it's literally a FOSS license). The only reason I can think of that you would even need to think about doing something extra to comply with the LPGL is if you release a Python app as a complete binary blob including the library, in which case you would need to have a method to allow a user to replace the library in the binary (but you could also just tweak your build process to exclude the library, either by patching aiohttp or by including a dummy version of the library). In the typical case for Python software, where the library is just depended on and pip installed, you would not need to do anything. |
Beta Was this translation helpful? Give feedback.
-
Hi, In case someone stumbles here, I have proposed a PR for that matter. |
Beta Was this translation helpful? Give feedback.
-
Great! Thanks to all for a great product! |
Beta Was this translation helpful? Give feedback.
-
I really like using aiohttp for the app I'm developing for work, but the legal team has raised a red flag regarding the use of
chardet
(orcchardet
), as it is LGPL-licensed. I've looked through the source, and see that its only usage is in theget_encoding()
method ofclient_reqrep.py
. I tried removing thatelse:
block, and everything runs fine, as we are not processing unknown blocks of text. I saw that you made it a required dependency back in 2015, but the license for it makes the entire aiohttp project not FOSS-compatible.Beta Was this translation helpful? Give feedback.
All reactions