- What would happen to the US Economy if taxes exceed 20% of GDP
- What is the economic incentive to cheat? How does an experiment capture exogenous deviations?
- Can my character have a pet mammoth?
- Where is the mention of Surya Loka(सूर्य लोकं) in Hinduism?
- Mysql_close ()-why few people apply
- 25x25 slitherlink puzzle
- Is there a quick way to speed up ICP in python using a cached KD-tree
- HC 05, Arduino Uno
- Remove lag between PS3 input via bluetooth to arduino
- Use esp32 as a secure sockets
- Best way to organize many pdf's?
- Is EPUB ready for most phones?
- Where is the fuel stored on an aircraft’s wing?
- What are the aileron lengths of commercial and military aircraft?
- Do jet aircraft have an emergency propeller?
- Are there different configurations of cabin crew seating arrangement for one aircraft model?
- How do PPL, CPL, and ATPL compare?
- To what extent is remuneration under a PPL enforced in the UK?
- What criteria are used for exiting an airplane in an emergency?
- Getting my dog ready to Adopt a new cat
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.