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? For example, can I take the async modules and build a commercial product on them? Cheers, -g -- Greg Stein, http://www.lyra.org/
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/)
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 medusa server has restrictive license, but the asyncore and asynchat modules use the standard Python license, with Sam Rushing as the copyright owner. just use the source...
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?
For example, can I take the async modules and build a commercial product on them?
surely hope so -- we're using them in everything we do. and my upcoming book is 60% about doing weird things with tkinter, and 40% about doing weird things with asynclib... </F>
participants (3)
-
Fredrik Lundh
-
Greg Stein
-
Guido van Rossum