A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-December/011032.html below:

[Python-Dev] Python 2.0 license and GPL

(offtopic) RE: [Python-Dev] Python 2.0 license and GPL (offtopic) RE: [Python-Dev] Python 2.0 license and GPLBarry A. Warsaw barry@digicool.com
Thu, 14 Dec 2000 19:33:16 -0500
>>>>> "GE" == Greg Ewing <greg@cosc.canterbury.ac.nz> writes:

    GE> I don't see how Q can *need* any particular library P to
    GE> work. The most it can need is some library with an API which
    GE> is compatible with P's. So I don't buy that argument.

It's been my understanding that the FSF's position on this is as
follows.  If the only functional implementation of the API is GPL'd
software then simply writing your code against that API is tantamount
to linking with that software.  Their reasoning is that the clear
intent of the programmer (shut up, Chad) is to combine the program
with GPL code.  As soon as there is a second, non-GPL implementation
of the API, you're fine because while you may not distribute your
program with the GPL'd software linked in, those who receive your
software wouldn't be forced to combine GPL and non-GPL code.

-Barry



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4