[Python-legal-sig] Include BSD code into Python?

[Victor Stinner]

2013/9/25 Jesse Noller <jnoller at gmail.com>:
> Maintaining the original copyright in python core is fine. Lots of files have that, and BSD headers

Ok, but where should we include the copyright notice for binary
Python? In the documentation? I see that the following page contains
many licenses:

http://docs.python.org/dev/license.html

Is it the right place to copy the copyright notice?

Victor

>
>> On Sep 24, 2013, at 6:29 PM, Ben Finney <ben+python at benfinney.id.au> wrote:
>>
>> Victor Stinner <victor.stinner at gmail.com> writes:
>>
>>> Can you confirm me that this BSD 3-clauses license is compatible with
>>> the Python license?
>>
>> Yes, it is compatible. This means that it is feasible to derive a work
>> from both the current Python and the work you're referring to, and
>> distribute the result as free software.
>>
>> Of course, all the terms of all the licenses must be simultaneously
>> satisfied when distributing that derived work.
>>
>>> I'm using libcfu hash table in my new tracemalloc module (PEP 454):
>>> http://hg.python.org/features/tracemalloc/file/ac693c811b1d/Modules/_tracemalloc.c#l1
>>>
>>> I heavily modified the code of the hash table, but I would like to
>>> keep the original author and the copyright notice.
>>
>> It's good that you would like that, because that's one of the terms you
>> need to satisfy in order to have license to distribute the work :-)
>>
>>> I contacted the author (Don Owens aka regexguy):
>>>
>>> me>> I would like to know if the BSD 3-clause license if
>>> me>> compatible with
>>> me>> the Python license
>>>
>>> don> I believe so.  It basically allows you to use the code any way you want,
>>> don> as long as you include the copyright notice and attribution in the code.
>>
>> Yes, where “the code” is any form of the code: i.e., distributing the
>> work in source form or binary form or any other form. To redistribute
>> the work under that license, the work's license text would need to be
>> included as part of the distributed derived work.
>>
>> In practice, that would mean CPython would need to incude the ‘libcfu’
>> copyright holder's name and the work's license text in every copy
>> distributed thereafter, or there would be no license to distribute the
>> resulting work.
>>
>> Whether that's acceptable to the PSF is a separate matter.
>>
>> --
>> \           “Kissing a smoker is like licking an ashtray.” —anonymous |
>>  `\                                                                   |
>> _o__)                                                                  |
>> Ben Finney
>>
>> _______________________________________________
>> Python-legal-sig mailing list
>> Python-legal-sig at python.org
>> https://mail.python.org/mailman/listinfo/python-legal-sig
> _______________________________________________
> Python-legal-sig mailing list
> Python-legal-sig at python.org
> https://mail.python.org/mailman/listinfo/python-legal-sig