Should license be LGPLv3 instead of GPLv3? #14
Description
As it stands (and to my understanding of the GPL), any Python program or package using blkinfo with its current GPLv3 license must be made available in its entirety as source code. That prevents a barrier to use of blkinfo.
I think the most Python packages that use a GPL variant use LGPL. With LGPL, if I included a modified version of blkinfo in a proprietary program then I would need to make the modified blkinfo source available, but not all the rest of the proprietary code. For example, psycopg2 uses LGPL
What's the intent here? If it is full GPL that's fine, but I thought I'd ask.