[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: calling octave from C
From: |
Judd Storrs |
Subject: |
Re: calling octave from C |
Date: |
Wed, 18 Nov 2009 18:13:18 -0500 |
Ok. I think you are overreaching by claiming that python scripts must
be GPLv3 as a result of using pytave.
1) Octave is an interpreter. The GPLv3 license does not apply to
interpreter input. e.g. m-files can be any license without violating
the interpreter's license.
2) python + pytave is also an interpreter. In order to distribute a
python + pytave interpreter, all components of the interpreter must be
GPLv3 compatible.
3) Python scripts are also interpreter input. They are equivalent to m-files.
--judd
- calling octave from C, Philipp Leser, 2009/11/18
- Re: calling octave from C, Jaroslav Hajek, 2009/11/18
- Re: calling octave from C, John W. Eaton, 2009/11/18
- Re: calling octave from C, David Grundberg, 2009/11/18
- Re: calling octave from C, Judd Storrs, 2009/11/18
- Re: calling octave from C, Judd Storrs, 2009/11/18
- Re: calling octave from C,
Judd Storrs <=
- Pytave licensing (was: Re: calling octave from C), David Grundberg, 2009/11/19
- Re: Pytave licensing (was: Re: calling octave from C), Ulrich Staudinger, 2009/11/19
- Re: Pytave licensing, David Grundberg, 2009/11/19
- Re: Pytave licensing (was: Re: calling octave from C), Søren Hauberg, 2009/11/19
- Re: Pytave licensing, David Grundberg, 2009/11/19
- Re: Pytave licensing, Ulrich Staudinger, 2009/11/19
- Re: Pytave licensing, David Grundberg, 2009/11/19
- Re: Pytave licensing, Ulrich Staudinger, 2009/11/19
- Re: Pytave licensing, David Grundberg, 2009/11/19
- Re: Pytave licensing, Jaroslav Hajek, 2009/11/19