On Thu, May 14, 2009 at 12:55:13PM -0700, Istvan Albert wrote: -> On May 14, 1:54?pm, Marek Szuba <mare...@gmail.com> wrote: -> -> > As far as I know, you are wrong here: Pygr neither is a derivative work -> > of setuptools-git nor links against it, -> -> But it does. You actually import this extension into setup.py via -> setuptools. What other way to use a python module extension is there? -> -> > process shouldn't affect Pygr's licensing any more than using GNU -> > Binutils to link our extensions -> -> That is not the same thing at all. You are using binutils to create -> another product. That is allowed. You do not import binutils into your -> python source. If you did it would need to become GPL. -> -> Incidentally I got nothing against GPL. And no one would ever bother -> us if we did not obey. But if people choose to release code via GPL we -> need to respect that.
FWIW, and IANAL, I believe that Istvan's interpretation is a reasonable one in this case. Correct, dunno -- but definitely arguable from what I've seen of the GPL. This sort of stuff is why I'm switching over to BSD- or (soon) Apache-like licenses for my own software. cheers, --t -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
