On 2023-02-03, Greg Ewing wrote:
> On 3/02/23 6:38 am, Jon Ribbens wrote:
>> If you change someone else's code then you have created a derived
>> work, which requires permission from both the original author and you
>> to copy. (Unless you change it so much that nothing remains of the
>> original
On 3/02/23 6:38 am, Jon Ribbens wrote:
If you change someone else's code then you have created a derived
work, which requires permission from both the original author and you
to copy. (Unless you change it so much that nothing remains of the
original author's code, of course.)
"Nothing" is prob
On 2023-02-02, Stefan Ram wrote:
> Many licenses in the Python world are like: "You can make
> changes, but have to leave in my Copyright notice.".
>
> Would it be possible that the original author could not
> claim a Copyright anymore when code has been changed?
No. If you change someone
On 31 Mar, 09:36, Duncan Booth <[EMAIL PROTECTED]> wrote:
>
> I don't have a printed copy, but Google Books has it (not sure which
> edition I found) and page xix says:
>
> Given the nature of the cookbook, we wanted the recipes to be usable under
> any circumstances where Python could be used. In
Paul Boddie <[EMAIL PROTECTED]> wrote:
> Note that the Python Cookbook says this about licensing: "Except where
> otherwise noted, recipes in the Python Cookbook are published under
> the Python license." The link is incorrect, but I presume they mean
> this licence:
>
> http://www.python.org/psf
Paul Boddie wrote:
> On 29 Mar, 20:24, DS <[EMAIL PROTECTED]> wrote:
>
>> I'm pretty sure this is the wrong place to ask, but I'm hoping someone
>> will point me in the right direction.
>>
>> I'm getting ready to publish a first open-source project written in
>> python. I am planning to use GPL
On 29 Mar, 20:24, DS <[EMAIL PROTECTED]> wrote:
> I'm pretty sure this is the wrong place to ask, but I'm hoping someone
> will point me in the right direction.
>
> I'm getting ready to publish a first open-source project written in
> python. I am planning to use GPLas the license. However, in my
Scott David Daniels wrote:
> DS wrote:
>
>> I'm getting ready to publish a first open-source project written in
>> python. I am planning to use GPL as the license. However, in my code,
>> there is a function that I like from Python Cookbook
>> So, my options appear to be:
>> 1. Don't u
DS wrote:
> I'm getting ready to publish a first open-source project written in
> python. I am planning to use GPL as the license. However, in my code,
> there is a function that I like from Python Cookbook
> So, my options appear to be:
> 1. Don't use it.
> 2. Use it with no comment --
On Sat, 27 Aug 2005 01:35:58 +0300, Christos Georgiou
<[EMAIL PROTECTED]> wrote:
>Your method is/will_not be free (as in beer), as hinted in
>http://www.ece.arizona.edu/~edatools/home/email/registry/Form-Sender01.htm
>. *That* is a drawback similar to the licensing of the Microsoft's
>Sender/Call
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?
--
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
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,
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
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
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
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
> "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
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
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
[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
21 matches
Mail list logo
