<br><br><div class="gmail_quote">On Sun, Jun 27, 2010 at 3:37 PM, <span dir="ltr"><<a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 26 Jun, 06:03 pm, <a href="mailto:sc@puzzlebox.info">sc@puzzlebox.info</a> wrote:<br>
>Hello-<br>
><br>
> I'm wondering if anyone can fill me in on the current status and<br>
>plans for Qt support under Twisted?<br>
<br>
</div>I think you nailed the status - it's an externally maintained reactor<br>
which probably works for some people. As far as plans for support go,<br>
there aren't really any. Most Twisted development happens without many<br>
specific plans though, so you shouldn't let that discourage you.<br>
<div class="im">><br>
> In the meantime, can anyone please update me if there has been any<br>
>further work or consideration towards official Qt support for Twisted?<br></div></blockquote><div><br></div><div>One issue with "official" support is PyQt licensing. If PySide is (or becomes) an alternative, the licensing issue would disappear and Twisted "could" include it in the distribution.</div>
<div><br></div><div>AFAIK, there hasn't been any substantial work on the qt4reactor beyond what exists on launchpad and github. I have a few patches aging in my inbox which fix some Mac platform problems etc.</div><div>
<br></div><div><snip></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"></div>
Perhaps Qt's networking support is on par with Twisted's, though, and<br>
such wouldn't be necessary. I don't know, as I have very little<br>
experience with Qt. I just wanted to mention the idea.<br></blockquote><div><br></div><div>The design of the qt4reactor was driven by the need to integrate two event loops. Qt has its own asynchronous event handling core which is exposed through PyQt. Fortunately, its fairly straightforward to register a callback for twisted "stuff" (time and file descriptors) and it all works pretty well... (meaning it passed Twisted's torture tests at the time it was checked into launchpad).</div>
<div><br></div><div>There is a non-traditional initialization using a non-blocking call to reactor.runReturn() which nails Twisted to PyQt. From that point on, Twisted behaves normally as does Qt / PyQt... The way god intended.</div>
<div><br></div><div>The more fundamental question, IMHO, is the status and critical mass of PySide. Nokia was unable to reach agreement with Riverbank which caused uncertainty after Qt's move to open source. I don't know where this stands.</div>
<div><br></div><div>If PySide is solid, and the API is similar to PyQt (which is the intent), porting qt4reactor to PySide is "probably" straightforward. I'm guessing that the qt4reactor remains functional as I've gotten email patches in the past few months.</div>
<div><br></div><div>I would offer to check this out but I can't promise any timeline. I'm willing to field questions on any coding bizarreness to the degree my brain hardening doesn't interfere.</div><div><br>
</div><div>-glenn</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Jean-Paul<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Glenn H. Tarbox, PhD || 206-274-6919 || <a href="mailto:glenn@tarbox.org">glenn@tarbox.org</a> - xmpp || ghtdak - aim,jabber,IRC,yahoo<br><br>