GPL and Python modules.

[Gerhard Haering]

On Mon, Oct 25, 2004 at 03:46:31PM +0000, Grant Edwards wrote:
> On 2004-10-25, Peter Otten <__peter__ at web.de> wrote:
> > Grant Edwards wrote:
> >
> >> Let's say I use a GPL'd python module (e.g. something installed
> >> in site-packages) in an application.
> >
> > I'd say everything that uses a GPL'd module is derived work
> > and must also be GPL'd. It doesn't matter how you distribute
> > it.
> 
> So my application code must be GPL'd even if I never distribute
> the module?  The mere act of inserting the line 
> 
> "import someGPLdmodule"
> 
> Makes my _source_code_ a derived work, and therefore must be
> GPL'd?  That just doesn't sound right.

The GPL only applies if you distribute your work (outside your
organization).

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 cra^w
questions.

Gerhard
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/python-list/attachments/20041025/d69d251c/attachment.sig>