Now that I have removed all GPL/LGPL code from scipy, I wanted to double check on the licenses of some NumPy code. In particular,
1. FreeBSD license: http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/core/include/numpy... http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/core/include/numpy...
2. Python license: SafeEval class in http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/lib/utils.py
Is there any need to look into getting the authors to re-license their code? The license are pretty liberal (and both look like they are compatible with the revised BSD license), but I thought I'd ask anyway.
Should we note the additional licenses in: http://projects.scipy.org/scipy/numpy/browser/trunk/LICENSE.txt
I was imagining something like: http://projects.scipy.org/scipy/scipy/browser/trunk/scipy/weave/LICENSE.txt
Thanks,
On Tue, Nov 11, 2008 at 02:12, Jarrod Millman millman@berkeley.edu wrote:
Now that I have removed all GPL/LGPL code from scipy, I wanted to double check on the licenses of some NumPy code. In particular,
- FreeBSD license:
http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/core/include/numpy... http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/core/include/numpy...
Fine.
- Python license:
SafeEval class in http://projects.scipy.org/scipy/numpy/browser/trunk/numpy/lib/utils.py
Fine (IMO, but I put that code in; get a second opinion). Users of numpy are already using Python and should be fine with those terms.