Embedding matplotlib in Tkinter Applications

Can you explain to me why you are so restrictive about GPLed code? I
mean, it's all OSS?

The licenses are very different: BSD (and MIT) do not impose a viral
copyleft. This is why Python is not GPL, nor is NumPy or Matplotlib.
People writing code under BSD-like licenses must carefully avoid viral
infection from GPL'd code.

Second, while John Hunter's views are not identical to mine, he
makes a collection of important points about licensing here:
http://neuroimaging.scipy.org/site/doc/manual/html/faq/johns_bsd_pitch.html
I'm going to treat John's note as enough of an answer to your question
unless you want more discussion.

Naturally, since you wrote the code, you get to choose the license, and
your choice is obviously none of my business. Hopefully that goes
without saying, but I'll say it to avoid misunderstanding.

Did you notice that it is not an example but an independent standalone
package? I'm not shure about this because you always talk about
"example". But maybe the summary is way too long, though ...

Since you posted this on Matplotlib, I assumed you wanted people to be
able to look at how you did it, not just use it. I am not diminishing
the application by saying it looks to be a nice example of how to embded
Matplotlib in Tk. If it were BSD-licensed I would probably get around
to looking at your code.

Alan Isaac

···

On 2/24/2010 2:36 AM, Friedrich Romstedt wrote:

Nor mine <wink>. I would say several things differently today -- here
is the version I wrote for the mpl docs:

http://matplotlib.sourceforge.net/devel/coding_guide.html#why-bsd-compatible

JDH

···

On Wed, Feb 24, 2010 at 7:14 AM, Alan G Isaac <alan.isaac@...287...> wrote:

On 2/24/2010 2:36 AM, Friedrich Romstedt wrote:

Can you explain to me why you are so restrictive about GPLed code? I
mean, it's all OSS?

The licenses are very different: BSD (and MIT) do not impose a viral
copyleft. This is why Python is not GPL, nor is NumPy or Matplotlib.
People writing code under BSD-like licenses must carefully avoid viral
infection from GPL'd code.

Second, while John Hunter's views are not identical to mine

http://neuroimaging.scipy.org/site/doc/manual/html/faq/johns_bsd_pitch.html:

Many people choose the GPL when releasing a package because it is the most famous open source license, and did not consider issues such as those raised here when choosing a license.

Alan, Thank you for your comment. I think I will release diagram_cl
as my first MIT project :slight_smile: Hope that it finds some users then. Also,
I consider switching to MIT license completely. In fact, I like it
much more, it's shorter, more concise, and you can use my software ...

I'm not shure whether someone can release software under GPL
incorporating MIT licensed software? Otherwise I would release under
dual license.

Friedrich

2010/2/24 Alan G Isaac <alan.isaac@...287...>:

···

On 2/24/2010 2:36 AM, Friedrich Romstedt wrote:

Can you explain to me why you are so restrictive about GPLed code? I
mean, it's all OSS?

The licenses are very different: BSD (and MIT) do not impose a viral
copyleft. This is why Python is not GPL, nor is NumPy or Matplotlib.
People writing code under BSD-like licenses must carefully avoid viral
infection from GPL'd code.

Second, while John Hunter's views are not identical to mine, he
makes a collection of important points about licensing here:
http://neuroimaging.scipy.org/site/doc/manual/html/faq/johns_bsd_pitch.html
I'm going to treat John's note as enough of an answer to your question
unless you want more discussion.

Naturally, since you wrote the code, you get to choose the license, and
your choice is obviously none of my business. Hopefully that goes
without saying, but I'll say it to avoid misunderstanding.

Did you notice that it is not an example but an independent standalone
package? I'm not shure about this because you always talk about
"example". But maybe the summary is way too long, though ...

Since you posted this on Matplotlib, I assumed you wanted people to be
able to look at how you did it, not just use it. I am not diminishing
the application by saying it looks to be a nice example of how to embded
Matplotlib in Tk. If it were BSD-licensed I would probably get around
to looking at your code.

Alan Isaac

Yes, GPL projects can use MIT or BSD code, but not vice-versa.

···

On Wed, Feb 24, 2010 at 8:17 AM, Friedrich Romstedt <friedrichromstedt@...287...> wrote:

I'm not shure whether someone can release software under GPL
incorporating MIT licensed software? Otherwise I would release under
dual license.

Ok, it's rereleased now under MIT,
github.com/friedrichromstedt/diagram_cl . I'm having somewhat trouble
accessing my web server at the moment, so please find it on github.
The docu on www.friedrichromstedt.org (see github link) is a bit
outdated, but only with respect to the double-right click settings
dialog.

Friedrich

Including the link http://www.friedrichromstedt.org/index.php?m=186 would be helpful;
it took a couple clicks to find it.

Also, apologies if you did and I do not recall, but posting to the
SciPy list might hook you up with more interested people. Be sure
to include a clear statement of the problem you are addressing.
(It is kind of buried in your introductory text.)

Cheers,
Alan

···

On 2/25/2010 6:22 PM, Friedrich Romstedt wrote:

Ok, it's rereleased now under MIT,
github.com/friedrichromstedt/diagram_cl . I'm having somewhat trouble
accessing my web server at the moment, so please find it on github.
The docu onwww.friedrichromstedt.org