Thanks for that response, Stephan.<br><br>I suppose I had in mind projects like <span style="font-style: italic;">cdat</span> which effectively redistribute Python. Developers /may/ wish to develop applications, and /may/ wish to distribute a python binary with their module already installed.
<br><br>If they were to do such a thing, they might need to be aware of licensing issues.<br><br>Cheers,<br>-T<br><br><div><span class="gmail_quote">On 3/21/07, <b class="gmail_sendername">Stephan Deibel</b> <<a href="mailto:email@example.com">
firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Tennessee Leeuwenburg wrote:<br>> I created a new project today at Google Code. I thought it might be
<br>> pretty cool to include a 'python software foundation' license option.<br>> This would allow python project developers to choose a license they know<br>> will be compatible with Python core, which may be an important
<br>> consideration. Perhaps also Google SoC submissions should use this also?<br><br>If there are going to be multiple developers on the project, and<br>there is a chance of adding the code to the standard library,<br>
then license choice is an issue. Otherwise, it doesn't matter<br>as far as the PSF is concerned.<br><br>This may be a bit off topic for this list, but on the other hand<br>it's pretty important that our advocates understand Python's
<br>licensing. So here are the key points if you want to facilitate<br>getting something into the standard library at some point in<br>the future:<br><br>* Get PSF contribution forms from all authors, or make sure you<br>
keep in contact with them so a form can be obtained later.<br> If code exists for which no form can be obtained, that would<br> block getting that module into the standard library.<br><br>* Use Academic Free License v.
2.1 or Apache License, Version 2.0<br> from the start if you don't want to have to change licenses<br> to contribute. Changing licenses is best avoided.<br><br>* For many things, the chances of going into the standard library
<br> are slim. However, it may still reduce the overall licensing<br> horrors of any future/mythical sumo distribution what does<br> contain your module.<br><br>* Be sure you understand the implications before using the GPL.
<br> For any library, using the GPL will greatly reduce your<br> potential contributor/user base. The LGPL is OK in most cases.<br> Of course there are perfectly valid reasons to use the GPL,<br> just don't make it your default blindly.
<br><br>See also:<br><br><a href="http://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq">http://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq</a><br><br>- Stephan<br></blockquote></div><br>