Mailman 3 October 2005 - Twisted

[Twisted-Python] How to force synchronous behavior
by Pedro Sanchez Oct. 31, 2005

Oct. 31, 2005

Hello, I want to encapsulate deferreds into a function that looks like synchronous when invoked. Something like this: def mySyncFunc() x = 0 def done(data): global x x = data d = someCalculation() d.addCallback(done) <something here to hold until "done" is really done> return x print mySyncFunc() someCalculation() returns a deferred (for instance to accesses a DB). So, how can I write mySyncFunc() so that at the end I print the result of … [View More]

14 31

[Twisted-Python] Trial and KeyboardInterrupt
by Jonathan Lange Oct. 30, 2005

Oct. 30, 2005

Trial and KeyboardInterrupt have had a long and chequered history (see http://twistedmatrix.com/bugs/issue628). I'd like to try to solve the problem once, and to never have it crop up again. To try to do this, I need effective unit tests for KeyboardInterrupt. However, I've got no idea on how to do this. Raising KeyboardInterrupt isn't enough. Please, someone, write (or tell me how to write) unit tests for Control-C interrupting the Trial process. Thanks, jml

1 0

[Twisted-Python] Newbie question - simpleclient.py crashes
by Frank Millman Oct. 30, 2005

Oct. 30, 2005

Hi all, I have just started looking at Twisted. I thought I would start by working my way through the examples. The first one I tried crashed on me! I can patch it to get it to work, but I would rather learn the exact reason for the crash, and the correct way to fix it. I am trying to run simpleserver.py and simpleclient.py, using RH9, Python 2.4.1, and Twisted 2.1.0. I start simpleserver from tty1, and then from tty2 I run simpleclient. This is the result (shortened) - Server said: hello, … [View More]

2 1

[Twisted-Python] Handling errors when using deferToThread
by Pedro Sanchez Oct. 28, 2005

Oct. 28, 2005

Hello, In the twisted documentation there is this example: from twisted.internet import threads def doLongCalculation(): # .... do long calculation here ... return 3 def printResult(x): print x # run method in thread and get result as defer.Deferred d = threads.deferToThread(doLongCalculation) d.addCallback(printResult) This works well as long as doLongCalculation() doesn't fail for any reason. But if it does, how can it trigger an errBack? I want to do something like this: … [View More]

3 4

[Twisted-Python] Re: [Twisted-commits] r14926 - Branch to obsolete setUpClass and tearDownClass
by Itamar Shtull-Trauring Oct. 28, 2005

Oct. 28, 2005

On Thu, 2005-10-27 at 20:21 -0600, Jonathan Lange wrote: > Author: jml > Date: Thu Oct 27 20:21:48 2005 > New Revision: 14926 > > Added: > branches/jml/trial-setupclass-death/ > - copied from r14925, trunk/ > Log: > Branch to obsolete setUpClass and tearDownClass Why?

1 0

[Twisted-Python] svn-reorg blocking
by Christopher Armstrong Oct. 28, 2005

Oct. 28, 2005

I really want to get svn-reorg finished up, because lots of people really want me to release Twisted sumo, and releasing sumo without svn-reorg is going to be very scary. Unfortunately, there's something blocking svn-reorg's merge: We haven't figured out a way to get the test suite to actually run with it. Trial, in trunk, looks for packages by traversing the filesystem. This doesn't work with packages made up of __path__s, which is how svn-reorg works. svn-reorg includes some changes to trial … [View More]

4 10

[Twisted-Python] IMAP4Client closes connection cleanly during search()
by Johannes Beigel Oct. 27, 2005

Oct. 27, 2005

Hello. I'm using twisted.mail.imap4.IMAP4Client and sometimes the connection gets closed cleanly "in the middle" of a command. This occurs (in a reproducible way) when I do imapClient.search(imap4.Query(all=True)) on a really big mailbox folder. The big problem is: Neither callback nor errback added to the Deferred from search() is called! I override factory.connectionLost() to get notified about the connection loss, but I'm not really sure what to do when I lose the connection (would … [View More]

2 4

[Twisted-Python] Re: [Twisted-commits] r14922 - Fix to replace a lambda with something that's safe in the scope when it's
by Jean-Paul Calderone Oct. 27, 2005

Oct. 27, 2005

On Thu, 27 Oct 2005 03:45:59 -0600, Matt Goodall <mg(a)wolfwood.twistedmatrix.com> wrote: >Author: mg >Date: Thu Oct 27 03:45:58 2005 >New Revision: 14922 > >Modified: > sandbox/mg/laxdb.py >Log: >Fix to replace a lambda with something that's safe in the scope when it's >actually executed .... just in case anyone else is actually using this thing. > Note that this changes the behavior from constructing Failure instances in the reactor thread to creating … [View More]

2 3

[Twisted-Python] Thoughts about testing
by Antony Kummel Oct. 27, 2005

Oct. 27, 2005

Hi all, I just want to share some ideas that I have had. >From my experience, testing with Trial is too hard. My problems can be divided into three categories: 1. obscure error reporting, 2. unclean reactor 3. whoop whoop whoop. I am also pretty sure that I'm doing things that Trial does not want me to do, such as actually opening sockets and communication over the network. I'm saying this because it does not seem to happen in the Twisted test-suite. But I don't think there is a good … [View More]reason for this limitation. Actually, in sum, I think there are too many limitations on writing tests with Trial, and they all boil down to the unclean reactor problem (or at least most of them). I want to suggest an alternative approach. How about not requiring the reactor to be clean at the end of a test? If anyone wants to make sure that anything they do leaves the reactor in a clean state, they can test for it themselves. This seems to me more like a constraint imposed by the implementation of Trial rather than a useful feature. Also, parts of Twisted itself are practically unusable inside a test because they leave the reactor dirty (such as threaded address resolution). An alternative feature could be enabling the user to specify that a certain delayed call or thread is allowed to remain after the test, and then Trial won't complain. The only question remaining is how to do it. Simple: use a different process. Run the tests in a different process, and create a new one each time the reactor is dirtied. py.execnet is a nice example of this concept. The second thought is this: there seem to be popping up different testing toolkits each with their own very nice extensions and features (http://testoob.sourceforge.net/, http://codespeak.net/py/current/doc/test.html). Trial cannot benefit from this, having branched away at the pyUnit level. I think Trial's special features can be relatively easily formulated as plugins to a plugin-oriented testing framework (especially if the clean reactor requirement is relieved), and so can the other testing packages. What this means, is that the best thing anyone who wants the world of unit testing to develop, and to benefit from it, is to push for a plugin-oriented pyUnit, and for an implementation of Trial (and the other tools) as a plugin for that framework. I think. Any comments? Antony Kummel __________________________________ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com [View Less]

12 19

[Twisted-Python] Twisted Jabber mailinglist
by Ralph Meijer Oct. 27, 2005

Oct. 27, 2005

Hi all, Recently I set up a mailinglist [1,2] for Jabber development using Twisted. I invited the developers from projects like pyMSNt, pyAIMt, pyICQt, PunJab and Twibber and the list now has 15 members. I invite everyone who is interested in Jabber development using Twisted to join. Also, Jp released Twisted Words 0.3 that saw a restucturing of the Jabber bits. The Twisted Xish project, that was changed in the same restructuring, has been folded in Words now. Xish should be usuable for non-… [View More]

9 17