[Python-Dev] licensing

Guido van Rossum guido at CNRI.Reston.VA.US
Tue Jun 8 04:09:02 CEST 1999

> Speaking of licensing issues...
> I seem to have read somewhere that the two Medusa files are under a
> separate license. Although, reading the files now, it seems they are
> not.
> The issue that I'm really raising is that Python should ship with a
> single license that covers everything. Otherwise, it will become very
> complicated for somebody to figure out which pieces fall under what
> restrictions.
> Is there anything in the distribution that is different than the normal
> license?

There are pieces with different licenses but they only differ in the
names of the beneficiaries, not in the conditions (although the words
aren't always exactly the same).  As far as I can tell, this is the
situation for asyncore.py and asynchat.py: they have a copyright
notice of their own (see the 1.5.2 source for the exact text) with Sam 
Rushing's copyright.

> For example, can I take the async modules and build a commercial product
> on them?

As far as I know, yes.  Sam Rushing promised me this when he gave them 
to me for inclusion.  (I've had a complaint that they aren't the
latest -- can someone confirm this?)

--Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list