Mailman 3 May 2008 - Twisted

回复： Re: [Twisted-Python] Re: Memory size of D eferreds
by arlenecc 21 May '08

21 May '08

原信息主题： Re: [Twisted-Python] Re: Memory size of Deferreds 发件人： Tristan Seligmann <mithrandi(a)mithrandi.net> 日期： 2008-05-21 11:38 * Martin Geisler <mg(a)daimi.au.dk> [2008-05-21 13:03:30 +0200]: > In particular, I guess you need to catch the QueueUnderflow exceptions > and then somehow know when it is time to call get() again. DeferredSemaphore may be more appropriate. -- mithrandi, i Ainil en-Balandor, a faer Ambar _______________________________________________ Twisted-Python mailing list Twisted-Python(a)twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python <<signature.asc>>

1 0

回复： Re: [Twisted-Python] Re: Memory size of D eferreds
by arlenecc 21 May '08

21 May '08

原信息主题： Re: [Twisted-Python] Re: Memory size of Deferreds 发件人： Tristan Seligmann <mithrandi(a)mithrandi.net> 日期： 2008-05-21 11:38 * Martin Geisler <mg(a)daimi.au.dk> [2008-05-21 13:03:30 +0200]: > In particular, I guess you need to catch the QueueUnderflow exceptions > and then somehow know when it is time to call get() again. DeferredSemaphore may be more appropriate. -- mithrandi, i Ainil en-Balandor, a faer Ambar _______________________________________________ Twisted-Python mailing list Twisted-Python(a)twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python <<signature.asc>>

1 0

[Twisted-Python] May Twisted Sprint this weekend
by Christopher Armstrong 20 May '08

20 May '08

What: Twisted Sprint Where: Divmod office, in Porter Square, Cambridge, MA When: 18 May 2008 Who: Anyone who wants to come Hi guys. There's a Twisted sprint at the Divmod office on Sunday, May 18th. At least Glyph, Jean-Paul, Itamar and I will be there; we're hoping Paul Swartz will show up and whoever else wants to come. If you'd like to come please respond and we'll tell you how to get there, etc. -- Christopher Armstrong International Man of Twistery http://radix.twistedmatrix.com/ http://twistedmatrix.com/ http://canonical.com/

3 3

[Twisted-Python] quitting clients connected to a server from serverside
by Patrick Scharrenberg 20 May '08

20 May '08

Hi! I have a server with multiple clients (processing nodes) which send their data periodically to the server using PB. Now I'm trying to quit the clients from the server-side, eg. when the server is shut down. I tried to install a "quit-callback-routine" from the client on the server, which the server should start if it wants a client to shutdown. But this doesn't work, instead I get a twisted.spread.jelly.InsecureJelly: method error. Please find attached some sample-code I used for testing. I think I was 'a little' to optimistic, that things just work when trying to send methods over the net and expecting twisted to know how to handle with this. But what do I have to change, to archive the result I'm expecting? Thanks in advance Patrick

2 3

[Twisted-Python] Question: Resuming a failed TCP transfer
by Nadav Aharony 19 May '08

19 May '08

Hi, I'm wondering, is there some built-in Twisted functionality (or any other existing implementation using Twisted) for doing resumable/disruption tolerant file transfer? Sample scenario: A sends file to B, session fails for whatever reason. B saved whatever data was received in some temporary structure, and knows to resume transfer from where it left off or alternatively request specific chunks that it is missing. Wanted to know this before I start implementing such functionality on my own. Thanks! Nadav

2 2

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com 17 May '08

17 May '08

1 0

[Twisted-Python] Adding a file dialog to wxacceptance.py breaks it
by Stephen Waterbury 17 May '08

17 May '08

The attached file is the example wxacceptance.py with a minimal modification to add a file selection dialog. If the file dialog is opened, the counting sequence stops, and although the gui menus still work and the gui is destroyed normally, it appears that the reactor hangs, and it has to be killed. (This example will not work with pre-2.5 versions of wxPython because I removed the compatibility code, which was getting deprecation warnings.) Let me know if I should just put this into a bug report. Platform: Ubuntu (gutsy) Twisted: 8.0.1-r23638 (latest svn) wxPython: 2.8.7.1 Thanks! Steve

1 0

[Twisted-Python] Change in reactor.stop() in Twisted 8.x
by Brian Granger 16 May '08

16 May '08

Hi, We have been using Twisted for a long time and are migrating to 8.0.1. We are finding that code that ran fine with 2.5.0 is giving problems with 8.0.1 and it appears to be related to what is happening in reactor.stop(). The code that is failing looks like this: ########## from twisted.internet import reactor d = doSomeThingThatReturnsADeferred() d.addCallback(handleOK) d.addCallback(lambda _: reactor.stop()) reactor.run() ########## The doSomeThingThatReturnsADeferred method is making XMLRPC calls underneath the hood. When we run this, it runs OK, but then blows up at the end with: Traceback (most recent call last): File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/defer.py", line 185, in addCallbacks self._runCallbacks() File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/defer.py", line 323, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/base.py", line 387, in _continueFiring callable(*args, **kwargs) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/base.py", line 524, in disconnectAll failure.Failure(main.CONNECTION_LOST)) --- <exception caught here> --- File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/python/log.py", line 51, in callWithLogger return callWithContext({"system": lp}, func, *args, **kw) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/python/log.py", line 36, in callWithContext return context.call({ILogContext: newCtx}, func, *args, **kw) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/python/context.py", line 59, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/python/context.py", line 37, in callWithContext return func(*args,**kw) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/tcp.py", line 577, in connectionLost self.connector.connectionLost(reason) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/base.py", line 937, in connectionLost self.factory.clientConnectionLost(self, reason) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/web/xmlrpc.py", line 325, in clientConnectionLost self.deferred.errback(reason) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/defer.py", line 264, in errback self._startRunCallbacks(fail) File "/Library/Python/2.5/site-packages/Twisted-8.0.1-py2.5-macosx-10.5-i386.egg/twisted/internet/defer.py", line 293, in _startRunCallbacks raise AlreadyCalledError twisted.internet.defer.AlreadyCalledError: I have checked and there is no failure object in my callback chain - this is internal to Twisted. Has the logic in reactor.stop changed recently? Any ideas about what would be causing this? Thanks Brian

4 4

[Twisted-Python] [RFC] Deprecation Policy
by Jonathan Lange 15 May '08

15 May '08

Hello everyone, Now that the release is out[1], I'd like to start work on fixing #1216 -- official deprecation policy. There's one proposed policy at http://twistedmatrix.com/trac/wiki/CompatibilityPolicy, there's also one mentioned in the ticket itself: deprecate in release N, remove in release N+1. Glyph has at one point expressed a desire for time-based deprecation.[2] I think these are all the questions we need to answer: - Is it time-based or release-based? - How long for? - Do we grade deprecations? How? - Which code is subject to this policy? CompatibilityPolicy suggests release-based deprecation that is graded over 4 releases: release N PendingDeprecationWarning, N+1 DeprecationWarning, N+2 DeprecationError, N+3 remove the functionality. Ticket #1216 suggests a release-based deprecation policy that is not graded and over 1 release: release N, add DeprecationWarning, release N+1, remove the functionality. Important factors to bear in mind: - Maintaining deprecated APIs brings a cost to developers when they maintain code. - Removing APIs brings a cost to users when they choose to upgrade. - We will probably always be changing APIs and making mistakes when we change them. Now, here's what I think. * Release-based, not time-based. Releases are easy to track, dates are less so. This is as true for Twisted programmers as it is for sysadmins & other Twisted users. I think that whatever problems are solved by time-based deprecation are better solved by regular releases. Our releases should, of course, be time-based. But that's another discussion. * Two release deprecation length. That is: release N, DeprecationWarning; release N+1, DeprecationWarning; release N+2, remove the functionality. This is enough to allow users to upgrade their version of Twisted incrementally. Trial has been doing one release for quite a while now, and I can't recall any complaints about breaking compatibility in released code. Micro-releases don't count. * No grading I think the DeprecationWarning vs PendingDeprecationWarning vs DeprecationError is too much hassle. Just say "next release" or "in two releases time". * All "public" code and command-line tools should be covered. Things marked as deprecated at the time of the 8.0 release should be grandfathered so as to be safe for removal. Anything else will get too confusing. The removal of the API stability markers agrees with this. Everything is public unless it starts with one underscore.[3] Most importantly, we should have a policy, we should all agree and as much of the policy as possible should be implemented in Python. This bug has been open for years now, and it is frustrating for the policy to change under one's feet or to disagree with other developers on something so fundamental. "Explicit is better than implicit". I'm sending this now because the 8.0 release is settling down and we have a sprint coming up where it might be easier to resolve this quickly. jml [1] I'm so happy. [2] http://twistedmatrix.com/trac/ticket/2352 [3] This hurts. t.trial.util doesn't begin with an underscore.

5 9

[Twisted-Python] Python logging with Twisted
by IloChab 15 May '08

15 May '08

I like Python logging module and I didn't feel comfortable with twisted log. So I was really happy to find the new PythonLoggingObserver in twisted last release. I wrote few modules that came in handy: 1) a NetworkHandler that uses a twisted connection to work with PythonLoggingObserver 2) a log server that offers a centralized log storage service to distributed twisted processes that connect to it via that NetworkHandler 3) a GUI to manage log files browsing and interactive dynamic configuration of logging behavior of any process connected to the server. I released them as a `twlogging` package on: http://sourceforge.net/projects/twlogging/ hoping that my work could be useful to someone else! Licia

2 3