Re: Python license and GPL programs
On Jan 16, Peter Eckersley wrote:
> IANAL either,
>
> but I did do some research into the matter, and you could add a caluse to the
> GPL which says something like:
>
> "If this program is used with Python interpreter code whose license contains a
> clause requiring legal disputes to be settled under the jurisdiction of the
> State of Virginia, USA, and whose copyright is owned by the Corporation for
> National Research Initiatives (CNRI) of Virginia, USA, then any legal action
> pertinent to such code, and where such a clause is enforceable, may be resolved
> under the jurisdiction of the State of Virginia, USA."
>
> This should give away the absolute minimum of concessions to be compatible with
> the Python 1.6+ license. Get a lawyer to look at it before you use it!
> Also, if you do get advice that it is okay, post so back here, so that I can
> put it in my code ;)
By this reasoning, for Python 2.0, you'd also have to add a BeOpen &
California clause. And god knows what jurisdiction 2.1 will be under
(I assume it will be owned by the PSF).
I guess I'm still missing how saying "you will interpret this license
under the laws of state X" has any effect on GPLed code. If it
doesn't matter under which state's laws you interpret the GPL, the
choice of state X doesn't matter; if it does matter, then the GPL is
flawed and we have much more serious problems than license
incompatibility.
Chris
--
Chris Lawrence <cnlawren@olemiss.edu> - http://www.lordsutch.com/chris/
Computer Systems Manager (Physics & Astronomy, 125 Lewis, 662-915-5765)
Instructor, POL 101 (Political Science, 208 Deupree, 662-915-5949)
Reply to: