Software licenses are generally a magical mystery to me Maybe you should have stopped there, because..
It makes your own source also need to be GPL and that you need to make your source code available. ..this is not true in any regard. I’ve spent significant time and effort into investigating various licenses and without going into too much detail, I can say that using libraries licensed under either GPL nor LGPL doesn’t have any effect on the code that *you write*; it is only concerned with code that you *modify* and then *distribute*. E.g. if you modify PyQt4 and then distribute that, you would be required to also distribute your changes. If you do not modify nor distribute, then as far as you’re concerned the library is entirely free to use forever. And again, have *nothing* to do with the code you write that uses the library. For us, this means nothing as we neither modify nor distribute PyQt4. To drive the point home; take this as an example of the flexibility you’ve got. You can write an entire application, say Maya, using PyQt. You can then distribute (e.g. sell) your application, and not include PyQt in your distribution but instead ask your users to install it themselves, and this is perfectly compatible with GPL. However, what you cannot do, is modify PyQt and call it “MyQt” and then re-license it under say New BSD. Your modified copy will also have to be GPL and this is where the “infectious” part of the license comes in. -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCxJtUbUSAjn2E7wGi8Vsg%3DCefP%3DQtD44b_6cFU40qAdA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.