I wish to release a non-commercial python application under GPL3 in both source and (PyInstaller) executable form. I'm struggling to find a consistent answer to the problem of imported modules.
Can I just put the usual GPL headers on my source files, include the GPL in COPYING and leave it at that?
Or do I have to collect together all the licences and source code (both python and, e.g. C/C++ dependencies) for everything that I import and include these in my distribution? I'm assuming that I don't, but reading the GPL3 licence suggests* that I do. Surely I don't have to ship the source for Qt, PyQt4, Numpy, Scipy, Matplotlib, Gdal etc. etc. in my distribution?
I also want to distribute a windows binary because the end users are unlikely to use the software if they have to run from source. This will package and re-distribute python and all the shared library dependancies. What are my legal obligations here with GPL? Are the imports 'Major Components' and therefore do not need to have the source distributed?
Section 1, Source code:
... The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code...