- How do you use the future of the verb devoir when using another verb aswell?
- clarify diffence between present, perfect, imperfect and pluperfect in French
- AR filter length
- (Faster) RCNN dataset physical markers
- how to create a DFT with scalloping/spectal leakage
- correctnes of multi prime RSA algorithm
- Can PRF F with generator P be secure?
- What to expect about the mobile phone usage during a flight to China and based on the CAAC regulations
- At what time of day does US visa expire?
- Travel Issues to Turkey
- Can a US green card holder transiting through China leave the airport? Recommendation for sight-seeing in Shanghai?
- Amtrak Seating NY to DC
- The soul as the form of the body – considering massive changes of the body
- Why can't uniformity of nature (in principle) be proven deductively?
- Need help to understand Kierkegaard's “An Ecstatic Discourse”
- Understanding Herr and its various meanings
- What is the english translation of ,,dagobertinisch"?
- How did they manage to make this song feel speeded?
- Writing a simple 12-tone row
- Hyperlink to a specific place in a document
Can a non-GPL 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++. The Python interpreter calls those C parts an "Extension", compiles as dynamically-linked library (.so or .dll), and loads during the runtime when I'm importing the library.
My concern arises from reading the GPL FAQ, where they state the following:
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.
However, when the interpreter is extended to provide “bindings” to other facilities (often, but not necessarily, libraries),
I am not a lawyer, and this is not legal advice.
I'm importing the library.
Importing the library essentially means you are linking to the GPL library. Hence, your program must also be GPL.
Obviously, this site generally prefers if you release all of your software under and open source license, but we realize this is not always feasible. Depending on your use case, there may be a way to use the library without licensing your entire project under the GPL. For example, you could create a wrapper for this library and then have your main program execute the wrapper via a python os.system() or subprocess.Popen() call. In this case, you would be required to release the wrapper under the GPL, but the main program could be released under a license of your choice (assuming no other licensing restrictions by the software stack you are using). Remember not to import your wrapper or the third party library in your main executable if you go this route.