Re: [Fwd: [gnu.org #220719] Re: python and gpl]

Tim Churches wrote: > Can't get much clearer than that. Whoops! Sorry about all the embedded HTML links, making it most unclear. Here is the relevant Australian law in a clearer form: COPYRIGHT ACT 1968 (as amended by the Copyright Amendment Act 2000) - SECT 47B *Reproduction for normal

Re: [Fwd: [gnu.org #220719] Re: python and gpl]

Richard Brodie wrote: "Tim Churches" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] 1) In Australia and Europe at least, loading program code from disc into memory in order to execute it is not considered as making an infringing copy under copyright law. I don't think it's as c

Re: [Fwd: [gnu.org #220719] Re: python and gpl]

"Tim Churches" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > 1) In Australia and Europe at least, loading program code from disc into > memory in > order to execute it is not considered as making an infringing copy under > copyright law. I don't think it's as clear cut as that.

Re: [Fwd: [gnu.org #220719] Re: python and gpl]

> "Paul" == Paul Rubin <"http://phr.cx"@NOSPAM.invalid> writes: Paul> Various possible candidates for such dragging have Paul> apparently decided that their chances weren't too good. Or simply that it wasn't worth the cost to go to court, even if they presumed they would eventually wi

Re: [Fwd: [gnu.org #220719] Re: python and gpl]

Tim Churches <[EMAIL PROTECTED]> writes: > See also this article, in which Lawrence Rosen, the attorney for > OSI, admits that it is impossible for anyone to properly interpret > the application of various open source licenses under the various > national laws: http://www.devx.com/opensource/Articl

Re: [Fwd: [gnu.org #220719] Re: python and gpl]

Steve Holden <[EMAIL PROTECTED]> wrote: > > In the absence of other information I Cc'd [EMAIL PROTECTED] to ask their > opinion about the relationship between GPL'd Python modules and > programs that imported them ... > > If a Python program imports a module licensed under the GPL, in your > >

Re: [Fwd: [gnu.org #220719] Re: python and gpl]

Steve Holden <[EMAIL PROTECTED]> writes: > In the absence of other information I Cc'd [EMAIL PROTECTED] to ask their > opinion about the relationship between GPL'd Python modules and > programs that imported them In the OP's particular case, he got the agreement of the GPL'd module's author, so it

[Fwd: [gnu.org #220719] Re: python and gpl]

In the absence of other information I Cc'd [EMAIL PROTECTED] to ask their opinion about the relationship between GPL'd Python modules and programs that imported them Original Message [EMAIL PROTECTED] - Mon Jan 31 15:49:28 2005]: Scott Robinson wrote: > On 30 Jan 2005 21:59:25

Re: python and gpl

Paul Rubin schreef: > My IANAL amateur reading is that the GPL does in fact apply, at least > in the US. Running the program is not restricted, but loading the > program from disk to memory before you can run it counts as copying > it, which invokes the license, Computer Associates v. Altai, 982

Re: Re: python and gpl

Paul Rubin wrote: > > Tim Churches <[EMAIL PROTECTED]> writes: > > >The question is: does shipping a backend which imports a module that > > > links with GPL code make some or all of the library GPL. > > We sought formal legal advice on this issue from a lawyer with > >

Re: python and gpl

Tim Churches <[EMAIL PROTECTED]> writes: > >The question is: does shipping a backend which imports a module that > > links with GPL code make some or all of the library GPL. > We sought formal legal advice on this issue from a lawyer with > expertise in open source licensing ...> > The answer was

Re: python and gpl

John Hunter wrote: I have a question about what it takes to trigger GPL restrictions in python code which conditionally uses a GPL library. Here is the context of my question. matplotlib, which I develop, is a plotting module which is distributed under a PSF compatible license, and hence we avoid

Re: python and gpl

Scott Robinson wrote: On 30 Jan 2005 21:59:25 -0800, Paul Rubin wrote: John Hunter <[EMAIL PROTECTED]> writes: The question is: does shipping a backend which imports a module that links with GPL code make some or all of the library GPL. Literally speaking, no, not automa

Re: python and gpl

On 30 Jan 2005 21:59:25 -0800, Paul Rubin wrote: >John Hunter <[EMAIL PROTECTED]> writes: >> The question is: does shipping a backend which imports a module that >> links with GPL code make some or all of the library GPL. > >Literally speaking, no, not automatically, any

Re: python and gpl

John Hunter <[EMAIL PROTECTED]> writes: > The question is: does shipping a backend which imports a module that > links with GPL code make some or all of the library GPL. Literally speaking, no, not automatically, any more than driving a car makes you into a licensed driver if you weren't one alrea

Re: python and gpl

John Hunter wrote: I have a question about what it takes to trigger GPL restrictions in python code which conditionally uses a GPL library. Here is the context of my question. matplotlib, which I develop, is a plotting module which is distributed under a PSF compatible license, and hence we avoid

Re: python and gpl

On Sun, 30 Jan 2005 22:25:10 -0600, John Hunter wrote: > The question is: does shipping a backend which imports a module that > links with GPL code make some or all of the library GPL. This > question is complicated, in my mind at least, by several factors. I believe the best and most honest answ