[Python-legal-sig] Including parts of weakref in Django

M.-A. Lemburg mal at egenix.com
Thu Jan 9 14:36:10 CET 2014


On 07.01.2014 10:25, Florian Apolloner wrote:
> Hi,
> 
> I am planing to backport weakref.WeakMethod to Django: 
> https://github.com/apollo13/django/blob/7a6c28977bf258b27c5bc2a19417f913c541e2dd/django/dispatch/weakref_backports.py
>
>  What I don't know is how the license information for that file should look like and if we do
> have the permission to include it like this. Could you please tell me how the license
> information should look like?

The standard Python license applies, so simply follow the rules
set forth in that license:

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

You essentially just need to retain all copyright notices, put the
license file into the distribution and include a list of changes.

> Thanks & best regards, Florian
> 
> P.S.: Please CC me, I am not on the list

I would prefer if the Reply-To list header were removed from this list.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Jan 09 2014)
>>> Python Projects, Consulting and Support ...   http://www.egenix.com/ 
>>> mxODBC.Zope/Plone.Database.Adapter ...       http://zope.egenix.com/ mxODBC, mxDateTime,
>>> mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::::: Try our mxODBC.Connect Python Database Interface for free ! ::::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611
               http://www.egenix.com/company/contact/


More information about the Python-legal-sig mailing list