Re: Licensing Python code under the Python license

Harlin Seritt wrote: If this is for making money, make it either a proprietary license or BSD. If you're giving it away and expect nothing for it except maybe fame, do GPL. You're kidding, right? How does the BSD license possibly offer more protection for a commercial program than the GPL does? --

Re: Licensing Python code under the Python license

Leif K-Brooks wrote: Harlin Seritt wrote: If this is for making money, make it either a proprietary license or BSD. If you're giving it away and expect nothing for it except maybe fame, do GPL. You're kidding, right? How does the BSD license possibly offer more protection for a commercial program

Re: Licensing Python code under the Python license

JanC wrote: This is difficult to do right, if you have to consider all the laws in different countries... Right. So he points out that his explanations are for US copyright law only, and then that legislation even in different US states, or perhaps even in districts, might be different. Therefore,

Re: Licensing Python code under the Python license

Martin v. Löwis schreef: > Larry argues that a license should be legally meaningful, and > legally clear - or else there is little point in formulating > a license in the first place. This is difficult to do right, if you have to consider all the laws in different countries... -- JanC "Be str

Re: Licensing Python code under the Python license

Ville Vainio wrote: Daniel> Thanks for the advice. I'll probably go with either the Daniel> BSD license, or possibly the LGPL. But I'm leaning Daniel> towards the BSD since it fits on the screen... Isn't MIT license even shorter and simpler? A while ago some Debian guys were speculati

Re: Licensing Python code under the Python license

When you ask an opinion, you can expect a long thread list... even if it's something inane like "What kind of license should I use?"... hacker/geeks/freaks/wannabes are only too happy to issue an opinion -- warranted or otherwise... Regards, Harlin Seritt -- http://mail.python.org/mailman/listi

Re: Licensing Python code under the Python license

If this is for making money, make it either a proprietary license or BSD. If you're giving it away and expect nothing for it except maybe fame, do GPL. :-) Regards, Harlin Seritt -- http://mail.python.org/mailman/listinfo/python-list

Re: Licensing Python code under the Python license

> "Daniel" == Daniel Keep <[EMAIL PROTECTED]> writes: Daniel> Thanks for the advice. I'll probably go with either the Daniel> BSD license, or possibly the LGPL. But I'm leaning Daniel> towards the BSD since it fits on the screen... Isn't MIT license even shorter and simpler? A w

Re: Licensing Python code under the Python license

Wow. That was fast. PHP forums eat your heart out :P Thanks for the advice. I'll probably go with either the BSD license, or possibly the LGPL. But I'm leaning towards the BSD since it fits on the screen... -- http://mail.python.org/mailman/listinfo/python-list

Re: Licensing Python code under the Python license

Daniel Keep wrote: I'm currently working on a Python program, and was wondering if it's possible to license the program, some associated tools, and a few other libraries I've written under the Python license. I had a look at the new PSF Python license on the list of OSI-approved licenses, but it ma

Re: Licensing Python code under the Python license

[Daniel Keep] > I'm currently working on a Python program, and was wondering if it's > possible to license the program, some associated tools, and a few other > libraries I've written under the Python license. > > I had a look at the new PSF Python license on the list of OSI-approved > licenses, bu

Licensing Python code under the Python license

I'm currently working on a Python program, and was wondering if it's possible to license the program, some associated tools, and a few other libraries I've written under the Python license. I had a look at the new PSF Python license on the list of OSI-approved licenses, but it makes numerous direc