RE: [pygame] pygame for commercial use

["S. Dagenhart" <vibrations@cetlink.net>]

Just to add to Pete's response, LGPL also states that you can modify the
original package for closed source projects as long as the modified code
is released back to the community. This is one of the beauties of LGPL
licensing, meaning you can keep your game/app sources private but must
release any modifications to existing pygame (or other LGPL'ed) sources
back to the community clearly marked as modified code and not as the
original package.

HTH,
Steven


-----Original Message-----
From: owner-pygame-users@seul.org [mailto:owner-pygame-users@seul.org]
On Behalf Of Pete Shinners
Sent: Sunday, October 31, 2004 7:59 AM
To: pygame-users@seul.org
Subject: Re: [pygame] pygame for commercial use

pygame@slippypeople.com wrote:
> Hello, I am hoping that some experienced pygame users/developers might
be able 
> to suggest some of the ramifications of using pygame in a commercial
setting. 
> I'd really like to know what the barriers are. For instance, a
particular 
> component has an overly restrictive license, a necessary feature is
lacking, 
> etc.

The license for Python, Pygame, and all the dependencies is friendly 
towards commercial projects. Pygame itself (and SDL) are licensed under 
LGPL. This basically means you can use Pygame without modification in 
any closed source projects. It's possible to package a project written 
in Pygame to appear the same as any native written game, even on most 
platforms.