Hi, I've just contributed a patch to CPython adding os.initgroups based on this extension module: http://svn.zope.org/Zope/trunk/src/initgroups/ The CPython ticket is here: http://bugs.python.org/issue7333 I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license? Thanks, Jean-Paul
exarkun@twistedmatrix.com wrote:
Hi,
I've just contributed a patch to CPython adding os.initgroups based on this extension module:
http://svn.zope.org/Zope/trunk/src/initgroups/
The CPython ticket is here:
http://bugs.python.org/issue7333
I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license?
I've passed this question along to the Zope Foundation. Regards, Martijn
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martijn Faassen wrote:
exarkun@twistedmatrix.com wrote:
Hi,
I've just contributed a patch to CPython adding os.initgroups based on this extension module:
http://svn.zope.org/Zope/trunk/src/initgroups/
The CPython ticket is here:
http://bugs.python.org/issue7333
I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license?
I've passed this question along to the Zope Foundation.
IMO, there isn't really much of anything "protectable" in that module: it is a micro-thin wrapper around a libc syscall. If I sat down to write the module from scratch, I bet I would come within a negligable diff (whitespace, ordering of #includes, etc.) of the same code. Just for belt-and-suspeders: as a ZF board member, I would certainly vote to contribute the code to Python. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksBdPMACgkQ+gerLs4ltQ5FIgCfY9O6Rix/Q1eqc3qLREP4zzM1 RB8AniYGBd+hhRCLlKbicPBVA8GrrGAA =B8bj -----END PGP SIGNATURE-----
Am 16.11.09 16:51, schrieb Tres Seaver:
Martijn Faassen wrote:
exarkun@twistedmatrix.com wrote:
Hi,
I've just contributed a patch to CPython adding os.initgroups based on this extension module:
http://svn.zope.org/Zope/trunk/src/initgroups/
The CPython ticket is here:
http://bugs.python.org/issue7333
I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license?
I've passed this question along to the Zope Foundation.
IMO, there isn't really much of anything "protectable" in that module: it is a micro-thin wrapper around a libc syscall. If I sat down to write the module from scratch, I bet I would come within a negligable diff (whitespace, ordering of #includes, etc.) of the same code.
Just for belt-and-suspeders: as a ZF board member, I would certainly vote to contribute the code to Python. Same here - discussing about this issue takes longer than writing the code from scratch :)
Andreas
On 11/16/2009 05:04 PM, Andreas Jung wrote:
Am 16.11.09 16:51, schrieb Tres Seaver:
Martijn Faassen wrote:
exarkun@twistedmatrix.com wrote:
Hi,
I've just contributed a patch to CPython adding os.initgroups based on this extension module:
http://svn.zope.org/Zope/trunk/src/initgroups/
The CPython ticket is here:
http://bugs.python.org/issue7333
I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license?
I've passed this question along to the Zope Foundation.
IMO, there isn't really much of anything "protectable" in that module: it is a micro-thin wrapper around a libc syscall. If I sat down to write the module from scratch, I bet I would come within a negligable diff (whitespace, ordering of #includes, etc.) of the same code.
Just for belt-and-suspeders: as a ZF board member, I would certainly vote to contribute the code to Python. Same here - discussing about this issue takes longer than writing the code from scratch :)
Another "me too". :) -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development
exarkun@twistedmatrix.com wrote:
I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license?
That was 4 out of 7 board members replying, so that's an official "okay" from the Zope Foundation board. Please go ahead. :) Regards, Martijn
On 05:29 pm, faassen@startifact.com wrote:
exarkun@twistedmatrix.com wrote:
I don't think there should be any licensing issues, as the ZPL is pretty permissive and the code is very short. However, if there are, could the code in question be relicensed for CPython under the Python license?
That was 4 out of 7 board members replying, so that's an official "okay" from the Zope Foundation board. Please go ahead. :)
Excellent. Thank you very much. Jean-Paul
participants (5)
-
Andreas Jung -
Christian Theune -
exarkun＠twistedmatrix.com -
Martijn Faassen -
Tres Seaver