Calling GPL code from a Python application

[Ernst Noch]

Mike Meyer wrote:
> Heiko Wundram <modelnine at bit-bukket.org> writes:
> 
>>I've asked TrollTech more than once for their stance on this, and each time
>>they have told me that it's illegal for me to develop an inhouse
>>application (such as a frontend to some webapp I've written that's only
>>used by us and will never ever be given away commercially) using the Open
>>Source edition of Qt (which I have not commercially licensed, of course,
>>which is way to expensive for me and Uni won't pay), unless I convince the
>>people at my univ to _release_ the code I've written under a GPL-compatible
>>open source license itself.
> 
> 
> I can't see how they could *require* you to release the code. The GPL
> certainly doesn't (or didn't) require that. Possibly they have a
> GPL-compatible license that adds that requirement.

No, they use the pure GPL. And that's what I was trying to get at in 
another post. What they are doing is prohibiting *in their commercial 
license* that you apply it on projects previously developed under the 
GPLed QT.

Obviously some individuals from the company have a different opinion, 
but I found another FAQ entry which states it clearly (note the phrase 
"non-opensource" in the question).

Note: Esp. concerning open source, I still think it's a good idea to 
repect the wishes of a rights owner even if the license he grants might 
be more permissive.

"""
Entry number: 190 - Using the Qt Open Source Edition, can I make 
non-opensource software for internal use in my company/organization?
Answer:

No. Software developed with the Qt Open Source Edition is always open 
source software, i.e. it can only be distributed under a open source 
software license. In particular, all the source code for all the modules 
your software is based on, regardless of whether they have been written 
by you or by others, must be open source software (because of the 
"viral" nature of the GPL). This is part of our commitment to the open 
source software community, and enables those who contribute to the open 
source software pool to do so without paying license fees.

Although it is possible to write open source software for internal use, 
it is difficult to ensure that such software is used and distributed 
legally. For example, if your open source software requires any modules 
that impose conditions on you that contradict the conditions of the GNU 
GPL, including, but not limited to, software patents, commercial license 
agreements, copyrighted interface definitions or any sort of 
non-disclosure agreement, then you cannot distribute it at all; hence it 
cannot be given to consultants, employees for their personal computers, 
subsidiaries, other divisions, or even to new owners.
Consequently we recommend using commercial licenses for all internal 
software development.

"""