On Sep 25, 2008, at 7:33 PM, Kevin Ar18 wrote:
>
>> Sorry for the confusion. It is the Apache license, as we found out
>> the PSF license can't be applied to anything but Python itself. If
>> Cython becomes part of the standard Python distribution, then we can
>> change to the PSF.
>>
>> I've changed LICENSE.txt t reflect this.
>>
>> - Robert
>
> There is also the option of a "generic PSF license" ... if that
> might be preferred. :)
>
> Per http://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq
> If you feel the PSF License is the one to use with your code, you
> must change the following parts of the license:
>
> * Replace all occurrences of "Python Software Foundation" and
> "PSF" with your name or organization.
> * Replace "Python" with the name of your project.
Yep. Actually, the reason we chose the license we did is on that same
page:
What if I want to contribute my code to the PSF?
The PSF does not want contributions of any code other than that which
will end up in Python or its standard libraries, or in Jython. If
your code is going to end up in Python or the standard library, the
PSF will require you to:
* License your code under an acceptable open source license.
These currently include only the Academic Free License and the Apache
License 2.0, although this list may be expanded in the future. (No,
the PSF License is not acceptable; see below)
* Fill out and submit a contributor agreement.
Though we haven't made any formal movements to have Cython as part of
the Python standard library, this is certainly something we would
like to consider in the future and we want to keep things open in
that direction. Fortunately the Apache License is a fairly widely
used and well known license, and matches well with our goals.
- Robert
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev
