Hi Kevin. I mentioned this on Ian's SQLObject list a couple of months
back. I did not want to go any further than to inquire about the
possibility of changing the license to MIT/BSD since this seemed to
arouse some strong feelings (about 'liberal' licensing vs GPLish licensing).
I am using SQL ORM for desktop as well as web so compiled becomes a
derivative work pretty much automatically as far as my read of
compiling. Also python byte compiles which is I feel a bit grey when
LGPL speaks of compiling. I had read that the folks with Twisted, as an
example, realized this ambiguity and changed the license to BSD as a
result. I am not a lawyer of course, but this concerns me enough to make
decisions to use of something consistent with the MIT/BSD as other
third party components of turbo gears stack (even though I like
SQLObject very much).
In any case, I am looking at TurboGears with much interest. I read your
blog earlier today and realize the best of best approach for TurboGears.
I support this initiative and of course realize that any development off
the beaten path on my part to incorporate anything Django with likely
only be of interest to perhaps a few folks.
Regards,
David
Kevin Dangoor wrote:
On 12/20/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The only trouble I am having has to do with SQLObjects licensing (since
python's bytecode generation is compiling in my view) and this leaves
things ambiguous with any project code generated (as far as SQLObjects
LGPL licensing). Personally, I believe SQLObjects is a great object
relational wrapper and I like it a lot. I wish the licensing were
different but I don't think that is about to change any time soon.
That's a very interesting read of the LGPL. I'd also prefer it if
SQLObject were MIT/BSD licensed, but that may be a difficult switch at
this point.
However, I don't think Ian Bicking's interpretation of the LGPL and
how it applies to users of SQLObject is the same as yours. Ian's on
this list so maybe he can comment, but I'm pretty sure that there is
nothing to fear in using SQLObject.
Kevin
