I have read with interest about sqlalchemy project, however the
licensing for the project is a concern to me. Byte compiling makes the
lgpl licensing ambiguous when it comes to python. There is also too much
language concerning the issue of compiling in the lgpl that confounds
the use of sqlalchemy in the development of compiled desktop applications.
If the intent is to create a broadly accessible and successful python
library and ORM, I am hoping the license for the project can be reviewed
and at the very least reconsidered. A BSD, MIT or python license
basically permits the library to be used in the widest sense - as braod
as python itself - while ensuring credit is given to the copyright
holder(s).
This looks like an interesting project and a library I would like to
have available in my python toolbox. I believe the best way of getting
sqlachemy used in projects is for the licensing to be comparable to
python's licensing itself so it is not an issue to consider whether it
will be used (as opposed to rejecting it for business applications where
companies are more sensitive about mixing with anything gplish).
I am not interested in a holy war over licensing since there can be
fairly strong view on either side. I am interested in useful ORM that I
can use on a routine basis to wrap sql in an nice way for python without
tripping over the license when developing for business clients.
Regards,
David
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Sqlalchemy-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
