The python license model

[Ramza Brown]

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?

I haven't worked with 'egg' too much.

--
Ramza from Atlanta
http://www.newspiritcompany.com

[Ramza Brown]

Ramza Brown 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?

I haven't worked with 'egg' too much.

Also, are there any articles for distributing python applications
without the default python install.

--
Ramza from Atlanta
http://www.newspiritcompany.com

[Aahz]

In article <tp********************@comcast.com>,
Ramza Brown <be**********@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 (aa**@pythoncraft.com) <*> http://www.pythoncraft.com/

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