Re: [pygame] LGPL and the PGU Library

[Phil Hassey <philhassey@xxxxxxxxx>]

Kris,

If you are planning on making a closed source or
commercial release of a product that makes use pygame,
SDL, or PGU, I advise you to contact a software lawyer
who can help you understand the LGPL as it applies to
your specific questions.  

Please also note that using py2exe with python 2.4 has
further complications with some Microsoft licenses. 
You will have to investigate those issues as well.

Sorry I can't be of more help, but I'm not a lawyer :)

Phil

--- Kris Schnee <kschnee@xxxxxxxxxx> wrote:

> Phil Hassey wrote:
> > Kris,
> > 
> > The LGPL is the same license that pygame uses. 
> Search
> > on google for information about the LGPL to
> understand
> > the license better.  There should be information
> > available on it, as it is one of the most commonly
> > used open source licenses.
> > 
> > the lgpl:
> > http://www.gnu.org/copyleft/lesser.html
> > 
> > this faq seems pretty helpful at explaining it (as
> > applied to another piece of software, but the same
> > answers would apply to pygame / PGU / SDL / etc.)
> > http://www.jboss.org/opensource/lgpl/faq
> 
> The FAQ makes it sound as though you can distribute
> the library to "work 
> with" your project, but not to build an EXE that
> includes the library. 
> But as I understand it, to build a Python EXE
> involves putting material 
> compiled from the libary into the EXE, so you then
> can't distribute a 
> Pygame-using application without also releasing all
> of your source code. 
> Or is it that the "libary" directory that Py2Exe
> creates within \dist is 
> self-contained, so that the LPGL's cooties don't get
> on my code?
> 
> Kris
> 
> 



	
		
______________________________________________________
Click here to donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/