Hello,
Reading Debian Weekly News, I learnt that there seem to be a problem
when importing an LGPL'd java library (this forces the importer to be
LGPL'd too), making the LGPL license equivalent to the GPL for Java
programs.
Here are a few references taken from DWN:
I'm by no way a license expert, but it seems to me that the import
mechanism in python is closer to Java's than what is allowed to use a
python LGPL'd library in a non GPL/LGPL program.
Could anyone confirm or infirm this impression?
--
Alexandre Fayolle
LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org
Développement logiciel avancé - Intelligence Artificielle - Formations
Reading Debian Weekly News, I learnt that there seem to be a problem
when importing an LGPL'd java library (this forces the importer to be
LGPL'd too), making the LGPL license equivalent to the GPL for Java
programs.
Here are a few references taken from DWN:
I'm by no way a license expert, but it seems to me that the import
mechanism in python is closer to Java's than what is allowed to use a
python LGPL'd library in a non GPL/LGPL program.
Could anyone confirm or infirm this impression?
--
Alexandre Fayolle
LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org
Développement logiciel avancé - Intelligence Artificielle - Formations
Comment