Steven D'Aprano wrote: > On Fri, 25 Nov 2005 11:30:46 -0800, mojosam wrote: > > >>I guess I don't care too much about how other people use it. > > > Then probably the best licence to use is just to follow the lead of > Python. For that sort of small program of limited value, I put something > like this in the code: > > Copyright (c) 2005 Steven D'Aprano. > Released under the same license as used by Python 2.3.2 itself. > See http://www.python.org/psf/license.html for details, and > http://www.python.org/2.3.2/license.html for the full text of the license. > > I use that as a no-brainer licence: it is weaker than but compatible with > the GPL, and requires less documentation. > Not only is this inappropriate, it doesn't even license users to use your software, it licenses them to use Python! The official advice of the PSF is that the unmodified Python license should *not* (and, really, can not) be used to license any other software.
regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC www.holdenweb.com PyCon TX 2006 www.python.org/pycon/ -- http://mail.python.org/mailman/listinfo/python-list
