[alexr1090]

Basically I'm wondering if what hoops, if any, you had to jump through. I read on the python web site that they don't mind you doing this, they just would like to know if you do. I've read the sites on the modules I'm using and what keeps coming up is the 'GNU GENERAL PUBLIC LICENSE'. It states in the license that

Quote

if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code.

Now does anyone know if that would apply to me if I wrote a program using a module that uses the 'GNU GENERAL PUBLIC LICENSE'?

Thanks for answering any of my questions.

[sepp2k]

My understanding (IANAL) is that if you use a GPL library, you have to license your own application under the GPL (or a compatible license) as well. That's why the LGPL is generally preferred for libraries.

The LGPL differs from the GPL in that it only applies if you create your own derived version of the library, not if you just use it. So you would be allowed to use the library in your own application and sell your application under whichever license you choose. If you also made improvements to the library itself, you would have to release those improvements under an LGPL compatible license though (which, in my mind, is perfectly fair).

Bottom line: If you see a library that's licensed under the GPL, not the LGPL, you should probably avoid it if you have commercial aspirations.

[no2pencil]

Wow, this is very interesting. A place I used to do some scripting work for was running a Windows Korn Shell. There was talk of them switching from Korn Shell to Python. I'll bet they didn't know this

[alexr1090]

sepp2k, on 28 December 2012 - 07:57 AM, said:

My understanding (IANAL) is that if you use a GPL library, you have to license your own application under the GPL (or a compatible license) as well. That's why the LGPL is generally preferred for libraries.

The LGPL differs from the GPL in that it only applies if you create your own derived version of the library, not if you just use it. So you would be allowed to use the library in your own application and sell your application under whichever license you choose. If you also made improvements to the library itself, you would have to release those improvements under an LGPL compatible license though (which, in my mind, is perfectly fair).

Bottom line: If you see a library that's licensed under the GPL, not the LGPL, you should probably avoid it if you have commercial aspirations.

Thanks for the reply, I've read several of your comments and have grown to respect your opinion, which is why that is particularly shitty to hear. I did a bit of googling and found the same thing. Damn.

[sepp2k]

no2pencil, on 28 December 2012 - 03:21 PM, said:

Wow, this is very interesting. A place I used to do some scripting work for was running a Windows Korn Shell. There was talk of them switching from Korn Shell to Python. I'll bet they didn't know this />

Didn't know what? Note that none of what was said in this thread is in any way specific to Python. Using a GPL library forces you to use GPL yourself, no matter which language your program or the library are written in.

Also note that Python or its standard library are not GPL. This question was specifically about third party libraries.

[no2pencil]

sepp2k, on 28 December 2012 - 09:40 AM, said:

no2pencil, on 28 December 2012 - 03:21 PM, said:

Wow, this is very interesting. A place I used to do some scripting work for was running a Windows Korn Shell. There was talk of them switching from Korn Shell to Python. I'll bet they didn't know this

Didn't know what? Note that none of what was said in this thread is in any way specific to Python. Using a GPL library forces you to use GPL yourself, no matter which language your program or the library are written in.

The product they were using was a closed source solution that they had rights to resell & also provide suport for. I know the GPL isn't specific to Python.

sepp2k, on 28 December 2012 - 09:40 AM, said:

Also note that Python or its standard library are not GPL. This question was specifically about third party libraries.

I thought that was what was being said. My mistake.

[jon.kiparsky]

What the GPL covers is modifications to a GPL-licensed work, not products created with that work.

Suppose I have a patented paintbrush and a copyrighted shade of red - you can use both of those to create an image which you own, completely. I have no rights in that image.


Now, if you include a library in your code, then you're covered by the terms under which you've licensed that library. This may "taint" your program with GPL-ness. If you want to write a program for sale, you should probably avoid using GPL-licensed libraries - LGPL may be okay, but IANAL. However, you're free to use GPL-licensed tools, like the gcc (though you should be careful, because the gcc comes with libraries which are GPL-licensed)

This post has been edited by jon.kiparsky: 28 December 2012 - 08:05 AM

[atraub]

This discussion is an excellent candidate for the advanced discussion forum. Moved!

[npanagakis]

I've heard that Galcon was written in Python. Not sure if its true though.