关于在商业代码中导入 GPL 版 Python 库的问题
我们正在评估几个用于图形操作的 Python 库。 我们尝试了“networkx”（http://networkx.lanl.gov/）和“igraph”（http://igraph.sourceforge.net/）。
虽然两者都是优秀的模块，但 igraph 由于其性质而速度更快 - 它是 libigraph 的 Python 包装器 - 一个快速的图形 C 库（使用 LAPACK 等）。
现在，igraph 库已获得 GPL 许可。 我的问题是：我可以导入 igraph 并在我的商业 Python 脚本中使用它吗？
（这是一个一般性问题，不仅限于 igraph。如果答案很明显，我深表歉意 - 我是许可证新手！）
谢谢， Raj
编辑：更具体地说，简单地导入 GPL Python 模块是否会使我的商业代码易于向公众发布？
We're evaluating a couple of Python libraries for Graph manipulation. We tried 'networkx' (http://networkx.lanl.gov/) and 'igraph' (http://igraph.sourceforge.net/).
While both are excellent modules, igraph is faster due to its nature - it's a Python wrapper over libigraph - a blistering fast graph C library (uses LAPACK etc).
Now, the igraph library is GPL licensed. My question is: Can I import igraph and use it in my commercial Python script?
(This is a general question, not just limited to igraph. Apologies if the answer is obvious - I'm a license-newb!)
Thanks,
Raj
EDIT: More specifically, does simply importing a GPL Python module make my commercial code liable to be released to the public?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
IANAL 等，但是：
自由软件基金会一直声称链接到 GPL 涵盖的库的软件是派生作品，因此需要由 GPL 本身涵盖（事实上，这是 LGPL 许可证的主要区别）。 我不知道各个司法管辖区的法院先例中的情况如何，&c，但如果您不想冒险就这个问题提起诉讼[这无疑会带来成本和糟糕的公关，即使它是最终成功]，如果您不想将源代码分发到代码中，避免链接到 GPL 库（包括动态链接）可能会更谨慎。
IANAL, etc etc, but:
The Free Software Foundation has consistently claimed that software linked to a library covered by GPL is a derived work, and thus needs to be covered by GPL itself (indeed, that's the main difference of the LGPL license). I don't know how the situation stands in court precedents in various jurisdiction, &c, but if you don't want to risk having to litigate on the issue [which would no doubt bring costs and bad PR even if it were to ultimately succeed], it may be more prudent to avoid linking to GPL libraries (including dynamic linking) if you don't want to distribute the sources to your code.
IANAL，但是：
是。 您可以编写商业软件并根据 GPL 分发它。 GPL 上的任何内容都不会阻止商业。 它甚至明确表示你可以随意出售你的软件，
不。 您不必发布任何内容。 您甚至不必分发任何东西。
如果您将程序分发给某人，则必须（仅向此人）提供源代码，并给予在同一许可证下修改和分发它的充分自由。
根据 GPL 分发某些内容或在代码中使用 GPL 库并不强迫您创建一个网站并将您的程序提供给世界上的每个人。
IANAL, but:
YES. You can write commercial software and distribute it under the GPL. Nothing on GPL prevents commerce. It even explicity says that you can SELL your software at will,
NO. You don't have to release anything. You don't even have to distribute anything.
If you ever distribute your program to someone, you must give (to this person only) the source code, and give full freedom to modify and distribute it under the same license.
Distributing something under GPL or using GPL libraries in your code doesn't force you to create a website and put your program for everybody in the world.
一些建议：
Some suggestions:
如果您的软件可以在不使用 GPL 代码的情况下使用而不损失任何功能，那么您的状态就相当不错了。 许多非自由程序都会使用 readline 库（如果可用），但默认情况下不会启用它，因此它们可以从它的存在中受益，但不会违反其许可证。 如果这些项目选择需要 readline 库进行行编辑，那么它们将属于 GPL 的范围并受其条款的约束。
If your software can be used without any loss of functionality without the use of the GPLed code, then you are in pretty good shape. Many non-free programs make use of the readline library, where available, but do not have it enabled by default, so that they can benefit from it's presence but not run afoul of its license. If those projects had chosen to require the readline library for line editing, then they would fall under the scope of the GPL and would be subject to its terms.
据我所知，GPL 许可证对于开源项目是免费的。
大多数图书馆都提供购买商业许可证以用于商业用途的选项。
联系图书馆的作者。
这取自 Wt 的网站：
As far as I know the GPL license is free for open sourced projects.
Most libraries provide the option to buy a commercial license for commercial use.
Contact the library's author.
This is taken from Wt's website:
您可能需要查看HOWTO：选择开源许可证及其第二部分。 它为您提供了一个决策树，为程序员建议许可证，并提供有关特定情况的详细信息。 这些文章也讲得很清楚了。
You might want to check HOWTO: Pick an open source license and its second installment. It gives you a decision tree that suggests a license for programmers, and gives details about specific situations. These articles are also quite clear.