--- On Thu, 5/13/10, Lawrence D'Oliveiro <l...@geek-central.gen.new_zealand> wrote:
> From: Lawrence D'Oliveiro <l...@geek-central.gen.new_zealand> > Subject: Re: Picking a license > To: python-list@python.org > Date: Thursday, May 13, 2010, 8:38 AM > In message <mailman.2834.1273453242.23598.python-l...@python.org>, > Ed Keith > wrote: > > > If, on the other hand you are releasing a library, to > be incorporated into > > other products, If you release it under the GPL I will > not take the time > > to learn it. I do not want to have to think about what > took I can legally > > use for what job. Libraries with permissive licenses > can be used in any > > project. Many contracts prohibit the use of GPL or > LGPL code. So I do not > > waist my time learning to use libraries covered by > restrictive licenses. > > So if you want me to even consider using your library > do not use GPL, or > > LGPL. > > What have you got against LGPL for this purpose? > -- > http://mail.python.org/mailman/listinfo/python-list > Most of my clients would not know how to relink a program if their life depended on it. And I do not want to put then in DLL hell. So I avoid the LGPL. -EdK Ed Keith e_...@yahoo.com Blog: edkeith.blogspot.com -- http://mail.python.org/mailman/listinfo/python-list
