wxPython/wxWindows Licensing Issues

wxPython Users
1

Hi All,

What exactly is the deal when it comes to distributing binaries of a wxPython-based product in a commercial environment? To explain, here is the scenario:

I develop an application in pure Python, that uses a particular release of wxPython, and another third party module (ctypes). Now, I want to distribute this to users, so I py2exe it up into a nice executable, and distribute the .exe (along with various wxPython .pyc files embedded inside), as well as a few additional support files (_ctypes.pyd, _sre.pyd, _winreg.pyd, python22.dll, wxc.pyd, and wxmsw240h.dll). My small Python-based program is part of a larger suite of tools which a customer pays money for (albeit a small amount). What are the licensing terms? I have looked into this and have basically just ended up more confused than when I started. Is wxPython covered by the library GPL, or the GPL? Do I have to distribute my source code? Do I need to copy and paste and provide a copyright blurb?
Ctypes is released under the MIT license which is pretty clear. The standard Python distribution is equally clear in terms of licensing. So - what about the wxPython and wxWindows stuff? Can anyone point me to a website or provide a nice summary?

Thanks,

···

--
Mark

2

What exactly is the deal when it comes to distributing binaries of a
wxPython-based product in a commercial environment?

The wxWindows license (which wxPython is under) is very clear. See
http://wxwindows.org/newlicen.htm

In my online help, I include a pointer to what I use and what their
licenses are:

http://bitpim.sourceforge.net/help/3rdparty.htm

Roger

3

Mark Melvin wrote:

What exactly is the deal when it comes to distributing binaries of a
wxPython-based product in a commercial environment?

wxPython shares the wxWindows license, which is essentially the LGPL.

http://wxwindows.org/newlicen.htm

Both it and the Python license should allow you to sell you app, just as
you are, without distributing source code...though you still could.

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer
                                        
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov

4

Mark Melvin wrote:

Hi All,

What exactly is the deal when it comes to distributing binaries of a wxPython-based product in a commercial environment?

In as small of a nutshell as possible, the wxWindows Library License *is* the LGPL but with 4 exceptions. The main one allows you to do whatever you want with distributing binaries of your application and the library.

Do I need to copy and paste and provide a copyright blurb?

No but it is a common courtesy to at least give attribution that the application uses the wxPython toolkit.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

5

Thanks very much for the responses:

[Robin Dunn <robin@alldunn.com> wrote:]

In as small of a nutshell as possible, the wxWindows Library License *is* the LGPL but with 4 exceptions. The main one allows you to do whatever you want with distributing binaries of your application and the library.

Yes - it was the exceptions that were unclear to me. Thanks for the "in a nutshell" - that's what I was hoping for.

Do I need to copy and paste and provide a copyright blurb?

No but it is a common courtesy to at least give attribution that the application uses the wxPython toolkit.

Will do - always like to give credit where it is due. We are proud of the fact that we have used wxPython - the problem is it is so good at what it does, no one is the wiser! Unless, of course they Ctrl-Alt-MiddleClick... ;o)

[Roger Binns <rogerb@rogerbinns.com> wrote:]

The wxWindows license (which wxPython is under) is very clear. See
http://wxwindows.org/newlicen.htm

I realize the license is clear - but I was confused as to whether or not wxPython followed this license exactly, and just what exceptions - if any - there were, as the GPL was mentioned for parts as well.

In my online help, I include a pointer to what I use and what their
licenses are:

3rd party components and licenses

This looks pretty cool! Since my application is for embedded device EEPROM programming, I have a particular kinship with this type of thing....fun ain't it?

[Chris Barker <Chris.Barker@noaa.gov> wrote:]

wxPython shares the wxWindows license, which is essentially the LGPL.

http://wxwindows.org/newlicen.htm

Both it and the Python license should allow you to sell you app, just as
you are, without distributing source code...though you still could.

Thanks, Chris. Yes - we are looking at the source code distribution thing. We are still converting our customers to Python - and it is going quite well!

Thanks,
Mark.