Contents
Can a non-Python Python program use GPL Python module?
Suppose I have a Python library which is distributed under the GPL license. I would like to use that library in my program, that I may eventually want to distribute under non-GPL terms. The library itself is not pure-Python: parts of it core functionality is written in C/C++.
Can a GPL library be dual license with MIT?
One caveat: you can also license your work under annother license. As long as people can get it under GPL, that satisfies the GPL requirements, and you can dual-license with MIT, for example. People can choose which license to follow. If I’m using a library that is licensed under GPL v3 in my project, can I license my project under the MIT license?
Do you have to license a GPL library?
If you use a GPL library in your project, that creates a derivative work of the library, and your entire project has to be licensed under the GPL. One exception: if it’s the LGPL (Lesser/Linking GPL) then dynamically linking the library does not create a derivative and you’re free to license how you want.
What kind of license do I need for Python?
In general, these licenses tend to fall into one of two categories: licenses that focus more on the user’s freedom to do with the software as they please (these are the more permissive open source licenses such as the MIT, BSD, and Apache)
Can a programming language interpreter run GPL-covered programs on it?
If a programming language interpreter has a license that is incompatible with the GPL, can I run GPL-covered programs on it? When the interpreter just interprets a language, the answer is yes. The interpreted program, to the interpreter, is just data; the GPL doesn’t restrict what tools you process the program with.
Do you have to be GPL to use GPL library?
Importing the library essentially means you are linking to the GPL library. Hence, your program must also be GPL. Depending on your use case, there may be a way to use the library without licensing your entire project under the GPL.
Which is an example of a GPL incompatible facility?
The JNI or Java Native Interface is an example of such a facility; libraries that are accessed in this way are linked dynamically with the Java programs that call them. So if these facilities are released under a GPL-incompatible license, the situation is like linking in any other way with a GPL-incompatible library.