Someone can give me some words about the license of wxpython?
If i make a program in pure python with wxpython as GUI
(i didnt any changes at sourcecode of both) can i release my *.py
files as creative common?
The user will have to download and install python and wxpython
before use the program.
Or i must to transform my *.py files with PyPy or CPython to
be able to choose some CC license for my program?
If yes can someone suggest some others package to do it?
Im asking this because the binary clause of wxwindows license makes
sense only when we talk about compiled languages like c++
I suppose most scripting languages like python, ruby, lua,
perl dont undertstand our scripts as derivative works since we
dont touch at source code of the scripting tool. Right?
"I am no lawyer"!
The way I understand the wxPython/wxWidgets license is that you can release/license your product which is using the wxPython library under whatever license you would like to.
I believe this is correct: under the LGPL, you are required to provide
the source code for any modifications you make *to wxPython/wxWidgets
itself*, but the application code can be under any license, whether
it's BSD, CC, GPL, or totally proprietary. Of course if you are
distributing it unmodified, no further action is needed to comply with
the license. (Just make sure you retain any copyright notices - which
is required - and acknowledge the use of wxPython - which may not be
required, but is good form anyway.)
-Nat
···
On Tue, Dec 11, 2012 at 6:18 AM, Werner <werner.bruhin@sfr.fr> wrote:
The way I understand the wxPython/wxWidgets license is that you can
release/license your product which is using the wxPython library under
whatever license you would like to.
Im really not sure about it. The question about the use of libraries in non compiled languages
like Python is still not a solid point of view. What the author understood when he choosed
license X has a weight. I guess the court understand my *.py files depends of that component
to work/run so... my program and the library are one. If they are one i have to follow the same
license. Some words of the author about this will be a relief.
The way I understand the wxPython/wxWidgets license is that you can
release/license your product which is using the wxPython library under
whatever license you would like to.
I believe this is correct: under the LGPL, you are required to provide
the source code for any modifications you make *to wxPython/wxWidgets
itself*, but the application code can be under any license, whether
it's BSD, CC, GPL, or totally proprietary. Of course if you are
distributing it unmodified, no further action is needed to comply with
the license. (Just make sure you retain any copyright notices - which
is required -
Correct. The wxWidgets license adds some exceptions related to distributing binaries (granting you a little more freedom than the LGPL) but that doesn't really apply if you are distributing your application as .py files.
and acknowledge the use of wxPython - which may not be
required, but is good form anyway.)
Agreed.
···
On 12/11/12 7:55 AM, Nat Echols wrote:
On Tue, Dec 11, 2012 at 6:18 AM, Werner <werner.bruhin@sfr.fr> wrote:
The way I understand the wxPython/wxWidgets license is that you can
release/license your product which is using the wxPython library under
whatever license you would like to.
I believe this is correct: under the LGPL, you are required to provide
the source code for any modifications you make *to wxPython/wxWidgets
itself*, but the application code can be under any license, whether
it’s BSD, CC, GPL, or totally proprietary. Of course if you are
distributing it unmodified, no further action is needed to comply with
the license. (Just make sure you retain any copyright notices - which
is required -
Correct. The wxWidgets license adds some exceptions related to
distributing binaries (granting you a little more freedom than the LGPL)
but that doesn’t really apply if you are distributing your application
as .py files.
and acknowledge the use of wxPython - which may not be