The python license model

Aahz aahz at pythoncraft.com
Fri Aug 12 02:08:23 CEST 2005


In article <tpGdnUh98pTjQ2bfRVn-tA at comcast.com>,
Ramza Brown  <berlin.brown at gmail.com> wrote:
>
>Can you distribute a python system with only a couple of libraries that 
>you plan to use.  For example, I generally avoid having a system with 
>hundreds of loose scripts(ie python library).  So, I have considered 
>only taking the libraries I need.  My question, is python license 
>friendly for doing this?

Dunno what you mean by "friendly", but aside from some little gotchas
having to do with its storied history, you can consider Python's license
functionally equivalent to BSD/MIT/Apache.  IOW, do whatever you want, as
long as you keep the copyright around.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

The way to build large Python applications is to componentize and
loosely-couple the hell out of everything.



More information about the Python-list mailing list