GPL and Python modules.

[Michael Hobbs]

Grant Edwards <grante at visi.com> wrote:
> On 2004-10-25, Gerhard Haering <gh at ghaering.de> wrote:
>> It would probably be a smart move to just *ask* the author of
>> the module if it's ok with him what you're planning to do.
>> Only if the two of you disagree, then you need to worry about
>> the legal questions.
> 
> I don't really want to have to come to individual agreements
> with 5-10 different module authors.  That's why "standard"
> licenses were invented.

It seems to me that any developer who releases a *library* under the
GPL falls into one of two camps:
A) The developer is unaware of the LGPL and/or the distinction between
the GPL and the LGPL.
B) The developer specifically intends to enforce the GPL on any
application that uses the library.

My guess is that 90% of all such developers fall into camp A. A simple
form email to each developer explaining the distinction and asking for
a license revision would probably resolve all problems.

If you happen to find a developer that falls into camp B, well, that's
his intent and there's not much you can do about it other than find a
different library.

-- Mike Hobbs