[Twisted-Python] Twisted & Qt

Bob Ippolito bob at redivi.com
Tue Sep 26 12:30:54 EDT 2006

On 9/26/06, glyph at divmod.com <glyph at divmod.com> wrote:
> On Tue, 26 Sep 2006 11:49:47 +0200, Tristan Seligmann <mithrandi-twisted-python at mithrandi.za.net> wrote:
> >* David Pratt <fairwinds at eastlink.ca> [2006-09-25 13:00:31 -0300]:
> >
> >> Hi Ed. Let's please leave the licensing issues of Twisted alone. This
> >> change was made quite some time ago as a license that would encourage
> >> developers to use Twisted. I think this should be respected and the
> >> licensing of code you are willing to commit, committed at MIT, so we
> >> don't need to open this debate.
> >
> >I was not under the impression that he was suggesting that Twisted's
> >license be changed; instead I believe he was merely trying to point out
> >that since Twisted code is MIT-licensed as a matter of policy, having
> >code that possible constitutes a derivative work of Qt may be legally
> >problematic.
> That's what I took away from it as well, and it turns out that he was correct.  There is a problem.
> I've gotten in touch with Riverbank Computing, the copyright holders on PyQt, and they are of the opinion that any Python code that imports "qt" is, in fact, a derivative work and therefore beholden to the GPL.
> I'll be removing it from the Twisted repository and contributing it to Riverbank for inclusion in PyQt at my next available opportunity.  This is probably going to require an immediate addition of a plugin API for reactors, so it can be loaded externally.

Maybe this is a good time to consider setuptools support? Entry points
are the external plug-in API that everyone else uses. Also, the fact
that Twisted can't be listed as a dependency in any setuptools-using
projects due to its non-standard setup.py is one huge pain in the ass.


More information about the Twisted-Python mailing list