Mailman 3 June 2003 - Twisted

[Twisted-Python] PATCH: twisted/coil/plugins/portforward.py docstring
by Lee Harr June 29, 2003

June 29, 2003

>cvs diff -u twisted/coil/plugins/portforward.py Index: twisted/coil/plugins/portforward.py =================================================================== RCS file: /cvs/Twisted/twisted/coil/plugins/portforward.py,v retrieving revision 1.2 diff -u -r1.2 portforward.py --- twisted/coil/plugins/portforward.py 5 Jun 2002 22:24:16 -0000 1.2 +++ twisted/coil/plugins/portforward.py 27 Jun 2003 22:36:28 -0000 @@ -14,7 +14,7 @@ # License along with this library; if not, write to the Free Software # Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA -"""Coil plugin for telnet shell.""" +"""Coil plugin for port forwarding.""" # Twisted Imports from twisted.coil import coil _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

2 1

[Twisted-Python] Some Question about on woven and rpy/page.Page
by Martin.Moellenbeck＠t-online.de June 28, 2003

June 28, 2003

Hello, I have setup a simple web-server (see the files attached). When I comment out the render-method of MyPage (start.rpy), I get this output: <snip> Some stuff goes here- this is the 'submit not in request.args' Some more stuff goes here. this is the None </snip> It seems the request parameter 'submit' are not set. If I comment in the render-method of MyPage, I get this output: <snip> send via submit <snip> When I have a look to the request, it seems that the first request (with the correct parameter, return with 302) and then a second request will be done with 200. Have anybody an answer for me ;-) Martin

2 2

[Twisted-Python] t.w.microdom and empty HTML elements
by Alex Levy June 27, 2003

June 27, 2003

While looking into a problem where my pages were showing up blank on IE, Moonfallen pointed me to the NEVERSINGLETON list in t.w.microdom.toxml(). There is a list of elements which should never be rendered as <node/>, and instead should always be <node></node>. Upon looking through the specs for XHTML at w3c.org, however, I found that the _only_ XHTML elements which are allowed as singletons are those whose content models are "EMPTY" -- <br/>, <hr/>, and so on. The list of EMPTY elements is not huge. I understand the issue that microdom cannot get bogged down with HTML tweaks; it is, after all, supposed to produce XML. But it seems like t.w.microdom shouldn't be spitting out invalid XHTML, even if (for now) it doesn't look like it breaks anyone's browser. As I understand it there is no real difference in XML between <node/> and <node></node>. Given that, wouldn't it be better for toxml() to use an ALLOWSINGLETON list instead of NEVERSINGLETON? That is, unless an element is explicitly allowed to be <foo/>, it would be <foo></foo>? If this is of interest to anyone, below is a diff that implements this; the list of elements is from the XHTML 1.0 DTD. I haven't tested it, so someone else will have to do that, but it works on my page. Index: twisted/web/microdom.py =================================================================== RCS file: /cvs/Twisted/twisted/web/microdom.py,v retrieving revision 1.93 diff -u -r1.93 microdom.py --- twisted/web/microdom.py 27 Jun 2003 19:10:35 -0000 1.93 +++ twisted/web/microdom.py 27 Jun 2003 20:16:17 -0000 @@ -449,8 +449,9 @@ def writexml(self, stream, indent='', addindent='', newl='', strip=0): # write beginning - NEVERSINGLETON = ('a', 'li', 'div', 'span', 'title', 'script', - 'textarea', 'select', 'style') + ALLOWSINGLETON = ('img', 'br', 'hr', 'base', 'meta', 'link', 'param', + 'area', 'input', 'col', 'basefont', 'isindex', + 'frame') # this should never be necessary unless people start # changing .tagName on the fly(?) if not self.preserveCase: @@ -468,7 +469,7 @@ for child in self.childNodes: child.writexml(stream, newindent, addindent, newl, strip) w(j((newl, indent, "</", self.endTagName, '>'))) - elif self.tagName.lower() in NEVERSINGLETON: + elif self.tagName.lower() not in ALLOWSINGLETON: w(j(('></', self.endTagName, '>'))) else: w(" />") -- Alex Levy WWW: http://mesozoic.geecs.org "Never let your sense of morals prevent you from doing what is right." -- Salvor Hardin, Isaac Asimov's _Foundation_

1 0

[Twisted-Python] flow testThreaded thingy
by Wari Wahab June 27, 2003

June 27, 2003

cce CVS wrote: >Modified files: >Twisted/twisted/flow/threads.py 1.3 1.4 > > It seems that flows testing can pass 1% of the time and most of the time, it'll stop on testThreaded, as seen in the screen dump below: testProtocol ... [OK] testProtocolLocalhost ... [OK] testThreaded ... [OK] testThreadedSleep ... [OK] testThreadedYield ... [OK] testZip ... [OK] testZipFailure ... [OK] ------------------------------------------------------------------------------- Ran 26 tests in 2.927s OK [wari@sync wari]$ trial -v twisted.test.test_flow twisted.test.test_flow FlowTest testBasic ... [OK] [..snip..] testProtocolLocalhost ... [OK] testThreaded ... From here, I tried doing strace on the process and just got this: gettimeofday({1056703375, 307699}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 308951}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 310242}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 311093}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 311504}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 312164}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 312646}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 313504}, NULL) = 0 select(8, [4 7], [], [], {0, 0}) = 0 (Timeout) gettimeofday({1056703375, 313888}, NULL) = 0 select(8, [4 7], [], [], {0, 0} <unfinished ...> [wari@sync wari]$ Infinitely, of course.. Have not really gone thru the code at all, but anyway, my machine specs are the typical ones you get from johncompanies.com, Redhat 8.0, python 2.2.1, dual CPU and 2GB of RAM.

3 4

[Twisted-Python] Patch for twisted.protocols.nntp
by Matthias Urlichs June 27, 2003

June 27, 2003

Since "suck" doesn't work for me for a variety of reasons, I decided to replace it with a solution based on twisted.protocol.nntp. After a few hours of hacking, I now have a nice program which nicely saturates my downlink bandwidth. ;-) To make a long story short, the attached patch implements the changes and fixes I needed to actually get there. The "Allow the article text to be a callable or deferred" change implements the common situation where I ask server B whether it would like to be fed article X before actually pulling that article from server A, and/or where the pull is still in progress. There is one somewhat- incompatible change here, in that I return the GROUP results (article count, high and low numbers) as integers, not as text. In practice they're going to be int()ized anyway, so this should not be a problem. # twisted/protocols/nntp.py # Fixes for news gateways / 'suck'-style operation / INN as server: # - The client uses \n and does NOT esacpe start-of-line dots. # The server uses \r\n and escapes dots ONCE, not twice (ouch). # - POST temporarily blocks streaming. Make sure this is observed, # pass a Deferred out for clients to restart themselves with # - Add a command to allow MODE READER # - Allow bare reply numbers without text # - Allow the article text to be a callable or a deferred # - use CHECK/TAKETHIS if there's a message ID # - return group article numbers (GROUP reply) as numbers # - Clean up article linefeed handling # twisted/test/test_nntp.py # Make sure that dot escapes are passed cleanly. # Make sure that no empty lines are added at the end. # Use the unittest object for checking. # Use client-side line endings for the client, # assume that the server side is transparent. # Make sure that the test doesn't just peter out halfway through. # Remove the commented-out iterate() calls. # loopback() already does the work for us. -- Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf(a)smurf.noris.de Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de -- Standards are different for all things, so the standard set by man is by no means the only 'certain' standard. If you mistake what is relative for something certain, you have strayed far from the ultimate truth. -- Chuang Tzu

2 6

[Twisted-Python] blocking code in object constructors
by Egor Cheshkov June 27, 2003

June 27, 2003

Hi, I need to do some blocking stuff in object constructor. However constructors can't return deferreds. The solution I see is to put all blocking initialization to some method and use factory to generate objects. Factory will return deferred wich will be called back when object initialization is complete. Is there Twisted Standard way to do such things? -- Egor Cheshkov

2 1

[Twisted-Python] flow threading fix (hopeful...)
by Wari Wahab June 27, 2003

June 27, 2003

cce CVS wrote: >Log message: >threading fix (hopeful...) > > I had to do a `kill -9` for this test, no other forms of murder works.

1 0

[Twisted-Python] more on flow testThreaded
by Wari Wahab June 27, 2003

June 27, 2003

cce CVS wrote: >Modified files: >Twisted/twisted/flow/threads.py 1.3 1.4 > One more thing, here's a traceback (when pressing CTRL-C), hope it helps. testThreaded ... Traceback (most recent call last): File "/usr/bin/trial", line 35, in ? run() File "/usr/lib/python2.2/site-packages/twisted/scripts/trial.py", line 311, in run suite.run(reporter, config['random']) File "/usr/lib/python2.2/site-packages/twisted/trial/unittest.py", line 313, in run test.runTests(output) File "/usr/lib/python2.2/site-packages/twisted/trial/runner.py", line 110, in runTests method, self.runTest).run() File "/usr/lib/python2.2/site-packages/twisted/trial/unittest.py", line 209, in run self.setUp_and_test() File "/usr/lib/python2.2/site-packages/twisted/trial/unittest.py", line 184, in setUp_and_test def setUp_and_test(self): self._runPhase(self._main) File "/usr/lib/python2.2/site-packages/twisted/trial/unittest.py", line 160, in _runPhase stage(*args, **kwargs) File "/usr/lib/python2.2/site-packages/twisted/trial/unittest.py", line 182, in _main self.runner(self.method) File "/usr/lib/python2.2/site-packages/twisted/trial/runner.py", line 100, in runTest method() File "/usr/lib/python2.2/site-packages/twisted/test/test_flow.py", line 401, in testThreaded self.assertEquals(result, unittest.deferredResult(d)) File "/usr/lib/python2.2/site-packages/twisted/trial/util.py", line 70, in deferredResult result = _getDeferredResult(d, timeout) File "/usr/lib/python2.2/site-packages/twisted/trial/util.py", line 63, in _getDeferredResult reactor.iterate() File "/usr/lib/python2.2/site-packages/twisted/internet/base.py", line 257, in iterate self.doIteration(delay) File "/usr/lib/python2.2/site-packages/twisted/internet/default.py", line 436, in doSelect [], timeout)

1 0

Re: [Twisted-Python] Issues 0.1 alpha release
by Jonathan Lange June 27, 2003

June 27, 2003

On Thu, Jun 26, 2003 at 02:20:51PM +1000, Richard Jones wrote: Content-Description: signed data > On Wednesday 25 June 2003 12:17 pm, Jonathan Lange wrote: > > Issues, a issue tracking system built on Twisted technology, has been > > released for the first time today! > > Could I ask why you've developed this from scratch rather than use Roundup's > core? > Sure. The answer is that I didn't know about it. No one has told me about Roundup, and it didn't stand out in any of my previous investigations into bug trackers (some of which were more than cursory). I guess I'll have to investigate Roundup further. Oops, jml

4 5

[Twisted-Python] Weird, apparently platform-dependent bug that hoses reactor
by Steve Waterbury June 27, 2003

June 27, 2003

Help! This is a bug that I discovered after I had just completed a change of name for one of the packages in my app, from "common" (bad name) to "enterprise" (sounds too broad but is actually appropriate in this case). Yes, I am using t.enterprise modules (adbapi) and yes, I've made sure that all our imports of that and of our module by that name (pangalactic.enterprise :^) are fully-qualified. The traceback we're getting is: Traceback (most recent call last): File "test_pger_get.py", line 37, in ? reactor.run() # start the main loop File "/usr/lib/python2.2/site-packages/twisted/internet/default.py", line 121, in run self.startRunning(installSignalHandlers=installSignalHandlers) File "/usr/lib/python2.2/site-packages/twisted/internet/default.py", line 115, in startRunning self._handleSignals() File "/usr/lib/python2.2/site-packages/twisted/internet/default.py", line 87, in _handleSignals signal.signal(signal.SIGINT, self.sigInt) SystemError: error return without exception set -------------------------------------------------------------- This is coming from a pretty simple test script that initializes some things and does a reactor.run() and prints the result or the error. (There's too much context to include all the code in this message, but I'll send it off-list to anyone who's interested.) The platform-dependent aspect is that we have run the exact same code on Debian (unstable) have *not* seen this traceback there. We get the traceback on a Red Hat 9 (2.4.20-18.9) machine. Basically curious if anyone else has seen anything like this. (We are still in the process of trying to narrow the differences between the code that ran -- before the module name change [big time sed script job] and after ... will post if we have a breakthrough.) Thanks! Steve

2 2