License about py-leveldb

[GoogleCodeExporter]

I may be mis-reading the LGPL, but why would it be forbidden?

See the first paragraph of http://www.gnu.org/licenses/why-not-lgpl.html:

The GNU Project has two principal licenses to use for libraries. One is the GNU 
Lesser GPL; the other is the ordinary GNU GPL. The choice of license makes a 
big difference: using the Lesser GPL permits use of the library in proprietary 
programs; using the ordinary GPL for a library makes it available only for free 
programs.

Is there a specific case you´re worried about?

Original comment by [email protected] on 18 Aug 2011 at 2:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It is not forbidden but more limited as with the new BSD license.
Because you also have to open the library source. With BSD license there is no 
such limitation.
Because of this a lot of companies don't use LGPL licensed software.

And py-leveldb is only a wrapper for leveldb which is BSD licensed.

Original comment by [email protected] on 18 Aug 2011 at 3:06

[GoogleCodeExporter]

You only have to open the library source if you modify it, right?

I'm not sure about the implications of your second point, but this library is 
simply bindings for leveldb, not sure why I called it a wrapper :).

Original comment by [email protected] on 18 Aug 2011 at 3:21

[GoogleCodeExporter]

Yes right, and even this is a problem in companies.
Don't ask why, but it is like this. Even I don't want to ask this in depth. ;-)

For me a wrapper and a simple binding is nearly the same.
My intention is to use the same license for both and don't restrict it further.

Original comment by [email protected] on 18 Aug 2011 at 3:27

[GoogleCodeExporter]

Alright. It is enough for me that the copyright notice ships with the 
source/binary, which I think leveldb does anyways.

Original comment by [email protected] on 18 Aug 2011 at 3:35

• Changed state: Accepted

[GoogleCodeExporter]

Yes, good news. Hope the license changes for the next release.
And in a fare future the module can go into the Python standard library.

Original comment by [email protected] on 19 Aug 2011 at 7:00

[GoogleCodeExporter]

Original comment by [email protected] on 13 Sep 2011 at 10:25

• Changed state: Done