Mailman 3 May 2004 - Twisted

[Twisted-Python] Where does the client stop the reactor?
by Bill la Forge May 15, 2004

May 15, 2004

I've noticed that when running an example client, the reactor shuts down cleanly, but it does not when running an example server. I've cludged some code for my testing that works fine for now, shutting down the reactor when there's no delayed calls: def stopWhenIdle(): count=len(reactor.getDelayedCalls()) if count: reactor.callLater(1,stopWhenIdle) else: reactor.stop() But where does the client normally stop the reactor? Thanks! Bill la Forge http://www.… [View More]

1 0

[Twisted-Python] Custom app using twisted
by Duncan McGreggor May 15, 2004

May 15, 2004

Don't know if this belongs on the list or not... I've just written a python monitoring program for baby-sitting a bunch of servers (I wanted something easier to setup and maintain than Nagios)... but the inevitable has happened, and I want to make a go-cart run like a ferrari. I was thinking of using python's interface to 'select' a la Medusa, but as soon as I saw 'import asyncore', I thought "There's got to be a better way..." Enter twisted. I would like to be able to run n monitoring … [View More]

1 0

[Twisted-Python] atop (was bsddb?)
by Bill la Forge May 14, 2004

May 14, 2004

I downloaded atop. The code is a bit denser than twisted, and I couldn't find much documentation. Any pointers? Also, are the mail archives available? Thanks! Bill la Forge http://www.geocities.com/laforge49/ Yahoo! India Matrimony: Find your partner online.

1 0

[Twisted-Python] bsddb?
by Bill la Forge May 14, 2004

May 14, 2004

New to twisted, interested in porting a project, but I can't find anything on using bsddb. I assume I need a dedicated thread. Has anyone else worked on this? (I did a web search, but couldn't relate what I found to any code in the 1.2 release I just downloaded. I also read the May list archive.) Thanks! Bill Yahoo! India Matrimony: Find your partner online.

4 4

[Twisted-Python] New email FeedParser
by Barry Warsaw May 13, 2004

May 13, 2004

At Pycon, I was talking with Glyph and others about the email parser in Python 2.3. Anthony Baxter, Thomas Wouters and I were having a little email-sig sprint, and we all agreed about the major problems with the current email parser. - It can throw exceptions parsing some messages. These exceptions can be difficult to handle. - You must slurp the entire message into memory before you can start parsing it. Over in the email-sig we've been talking and working on a new parser, called the … [View More]FeedParser which eliminates both of these problems. This parser also has the advantage of being much more RFC compliant, IMO <2046 wink>. In fact, we now have a new FeedParser.py in Python 2.4cvs (slated to be email 3.0) which I think does a very good job of parsing all manner of valid and invalid emails. The old email.Parser.Parser interface continues to exist for backward compatibility. The docs have not been updated yet, but the unit tests have. Note that the FeedParser, if it encounters broken MIME, will add 'defects' to a message object and continue on as best it can. You can check the message's .defects attribute; if it exists it will be a list of instances providing more information about what type(s) of defects were encounter. To use it, you instantiate an email.FeedParser.FeedParser and continually call its .feed() method, which takes a single argument of arbitrary length string data. The data need not be a complete line, although the FeedParser will split it into lines (using any of the three common line endings), gulping input a line at a time. Internally, the parsing routines are generators that yield when they need more data (feed() itself just returns). When you've feed it all the data there's ever going to be, you call .close() on the parser; the rest of the data is consumed and you get back the root email object. Because I think we're largely done with the FeedParser[1], and because some of the Twisted guys were interested in this stuff, I'm sending this message so you can grab the new parser and see if it's going to fit the bill. For now, you'll have to get it out of Python's cvs, but at some point when we've addressed the other issues in the email package, we'll make a distutils release. Note that email 3.0 will be compatible with Python 2.3 but nothing earlier. Please follow up with any discussions to email-sig(a)python.org. Enjoy, -Barry [1] Although see these messages for open issues: http://mail.python.org/pipermail/email-sig/2004-May/000114.html http://mail.python.org/pipermail/email-sig/2004-May/000118.html [View Less]

1 0

[Twisted-Python] PB locally logging errors from deferreds in remote_* methods
by David Bolen May 13, 2004

May 13, 2004

I was wondering if anyone knew the rationale for why Twisted's PB logs any errors (using log.err) that may be returned from a deferred that has been returned in response to a remote_* call on a pb.Referenceable object? It seems like a fairly standard situation, where the error is just something to be reflected back to the client. For example, I've got a series of components in a system I'm working on that were designed from the beginning to return deferreds from their APIs, even when they … [View More]

1 0

[Twisted-Python] Getting error code
by Sorin C. May 13, 2004

May 13, 2004

Hi, Is there a way to extract the error code from a Failure instance? For example when clientConnectionFailed is called the 'value' field of the Failure instance is 'Connection was refused by other side: 10061: Unknown error.'. Can I get 10061 somehow as I don't feel safe parsing this string. Thanks, Sorin __________________________________ Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' http://movies.yahoo.com/showtimes/movie?mid=1808405861

2 2

[Twisted-Python] XML-RPC & objects that won't serialize
by James R. Saker Jr. May 13, 2004

May 13, 2004

Steve writes: >...then converting them back to mx.DateTimes with DateTime.ISO.ParseDateTime. Not elegant, but it does the job. Note that PB's jelly will also complain about DateTimes. Yes; I also resorted to converting them before passing back to the client. Was curious if there was a better way. Per Federico's post, I actually started with psycopg but found several twisted references to preferring pyPgSQL. I tested with about 110,000 records passed (in about 15-20 seconds - most of which … [View More]

2 1

[Twisted-Python] adbapi/postgresql and xml-rpc
by James R. Saker Jr. May 12, 2004

May 12, 2004

Have a design question to pass to the list. I've gotten my distributed app working - pulling snort data from a postgresql database via twisted's adbapi and handling via xml-rpc - though xml-rpc is screaming about not being able to serialize postgresql's timestamp format. For instance, this query works (using a query test client and a "take any SQL string in and process it" xmlrpc method on the server local to database): # snipped python code setting things up. here's the xmlrpc call: (answer,… [View More]

3 3

[Twisted-Python] When do calls to transport.write() block ?
by Stefan Behnel May 11, 2004

May 11, 2004

Hi everyone! I have looked through quite a bit of Twisted's code by now, but I just can't manage to figure out how those transport.write()s work. The servers I looked through always come back to this without putting any special treatment into it. My question is: If a server starts sending as fast as it can, what will happen to the output queue? Will Twisted just eat up all memory with buffers? Will it start blocking? Will it open up a thread? What will it do? Since this really is an … [View More]

3 5