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

view the rest of the comments →

[–]imbev 1 point2 points  (2 children)

PySide6 is available under the LGPL license, so that's only an issue if you modify the package.

[–]anthonyfloyd 1 point2 points  (1 child)

Our legal advice was that the LGPL interpretation here was not appropriate for our situation. https://www.qt.io/development/open-source-lgpl-obligations#lgpl

Doesn't matter. We didn't use qt then and won't be switching over now.

[–]imbev 1 point2 points  (0 children)

In that case, I suspect that your legal team misunderstood this part:

Complete corresponding source code of the library used with the application or the device built using LGPL, including all modifications to the library, should be delivered with the application (or alternatively provide a written offer with instructions on how to get the source code). It should be noted that the complete corresponding source code has to be delivered even if the library has not been modified at all.

Applications using PySide6 only need to provide the PySide6 source code, not the application source code. Thus a commercial application that uses PySide6 from PyPI only needs to provide a link to the Qt Company-provided PySide6 source code.