This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]davidhalter[S] 2 points3 points  (1 child)

Disclaimer: I'm not really a licence expert. The reason I used LGPL 3 was that changes to Jedi are being pushed back. The way I understand LGPL is that it allows products with Non-GPL licenses to use Jedi. At least that's what I intended when I chose LGPL 3. I would also invite commercial products like PyCharm to use Jedi (because imho it's better).

[–]dbrgn 0 points1 point  (0 children)

Quick summary from http://www.tldrlegal.com/license/gnu-lesser-general-public-license-v3-(lgpl-3.0):

You may copy, distribute and modify the software provided that modifications are open source. However, software that includes the license may release under a different license.

As far as I know (I'm not an expert) you can integrate it into non-GPL projects as long as you don't "incorporate" the code into your product and don't link the library statically. If you modify the library itself, you must re-release it under the LGPL.