On Thu, 2009-10-08 at 21:03 -0400, Mark Visser wrote:
> Is there a project underway to port Twisted to Python 3.x?
Not at the moment. Supporting both 2.x and 3.x is harder than it should
be, and all of Twisted's users (and almost all Python users) use 2.x.
-Itamar
_
On Thu, 2009-10-15 at 00:01 -0400, Steve Steiner (listsin) wrote:
> Hey!
>
> I apologize in advance if this type of request is not desired/allowed
> on this list.
Nope, it's fine. You might also want to post to the twisted-web list.
> I'm looking for a very short-term mentoring/con
You might also try the twisted-web list.
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On Mon, 2009-11-02 at 21:11 +0600, Artem Bokhan wrote:
> Hello!
>
> I'm playing with reverse proxy from examples
> (Twisted-8.2.0/doc/web/examples/proxy.py). May somebody explain what
> part of code uses threads there?
>
> pstree -p | grep python
>
> -python(12786)-+-{python}(12795)
>
On Wed, 2009-11-18 at 06:03 -0800, Tommaso Mazzafico wrote:
> I tried this code:
>
> -
> from twisted.spread import pb
> from twisted.internet import reactor
>
> class Echoer(pb.Root):
>def remote_echo(self, s):
> return s
> if __name__ == "__main
On Wed, 2009-11-18 at 18:22 -0500, vit...@synapticvision.com wrote:
> hi,
> is there any example how to implement long-polling channel with
> Twisted while using reactor()?
What is a "long-polling channel"?
___
Twisted-Python mailing list
Twisted-Pyt
On Sat, 2009-11-28 at 15:05 +0200, MārisR wrote:
> I wondering if its possible to load utidylib in thread, do processing
> and after this kill thread and release memory? Or maybe something like
> deferToProcess?
1. You should report the bug to the utidylib authors, so they can fix it
or pass it o
On Tue, 2009-12-08 at 13:50 +0100, Gabriel Rossetti wrote:
> I have to send a message just before my service quits, but sometimes the
> reactor quits before the msg is sent.
> I was wondering if I should user reactor.callLater like so :
...
> (which I don't really like), or use reactor.callFromThr
