Mailman 3 September 2013 - Twisted

[Twisted-Python] Buildbot downtime
by Tom Prince March 3, 2022

March 3, 2022

I am plannig to upgrade twisted's buildbot in the near future. In preperation for that, I am going to take down the production buildbot on Tuesday, June 26, around 1600 UTC[1]. During that time, the result of any builds done will be lost. Thus, I'd ask that people avoid committing to trunk during that time. I will send a reminder before I take down the buildbot both here, and on #twisted and #twisted-dev. Tom [1] http://timeanddate.com/worldclock/meetingtime.html?iso=20120626&p1=80&p2=22…

2 8

[Twisted-Python] Twisted Python 0.7.0 Prerelease Testing
by Glyph Lefkowitz Aug. 5, 2021

Aug. 5, 2021

hi there, folks: I'd really like to release 0.7.0 but I would like it to be at least a little bit tested before I do so. Could those of you with CVS trees check everything out and see if it performs as advertised? Deeper bugs than that will have to wait for the next release, but I'd at least like to know if it works for someone other than me. Thanks. ______ __ __ _____ _ _ | ____ | \_/ |_____] |_____| |… [View More]

4 5

[Twisted-Python] Real Viagra Professional - for real sex pros
by Tamika May 1, 2019

May 1, 2019

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <center> <a href="http://rqf.entercompassion.com"><img src="http://mediapix.ru/pics/685207b3dd437eff7f15c0744b5c1d3a.gif"> <title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <link rel="stylesheet" href="http://gfx8.nnt.com/mail/12.0.1187.0824/positioning.css" /> </head> <body style="overflow:auto;"… [View More]> <div id="PrintShellToolbar"> <div class="ContainerPadding"> <span class="FloatRight"> <a href= > <img alt="" src="http://gfx1.nfi.com/mail/w2/pr02/ltr/glyph_close_rest.gif" /> <Close window> <a href= > <img alt="" src="http://gfx2.czb.com/mail/w2/pr02/ltr/i_print.gif" /> <Print> </a> </span> </div> </div> <div> <div class="BorderContainerOutline ContainerPadding"> <div class="ClearBoth"> <span class="HeaderData" style="font-size:large;"> <TuPostal.com Cambia de nombre?> </span> </div> <div class="ClearBoth"> <span class="HeaderLabel"> <From:> </span> <span class="HeaderData"> <b><TuPostal.com></b> </span> </div> <div class="ClearBoth"> <span class="HeaderLabel"> <Sent:> </span> <span class="HeaderData"> <div class="ClearBoth"> <span class="HeaderLabel"> To: </span> <span class="HeaderData"> Mikelelliott (mikelelliott(a)rlo.com) </span> </div> <br /> </div> </div> <div class="MessageBody" style=""> <br /> <div id="MessageBodyText" class="ExternalClass" style="border: 1px solid #fff ;"> <pre>Hola!<br> <br>Tupostal es ahora parte de Sonico!<br> <br>Para conocer nuestro nuevo sitio, haz clic en el siguiente link:<br><a href='http://www.gwpcom/index1.php' target='_blank'>http://www.bjncom/index1.php</a><br> <br>Sonico es un sitio donde puedes...<br>- Guardar fotos ilimitadas<br>- Re encontrarte con viejos amigos<br>- Recibir novedades de tus amigos.<br> <br>Te Esperamos! Ya somos mas de 21 millones de usuarios!!<br> <br>Sonico - Amigos Conectados<br> <br> <br>PD: Ahora tambien podras guardar tus postales<br> <br> <br>------------------------------------------<br>Haz recibido este email porque te encuentras registrado en fdm.com.<br>Si no deseas recibir mas mensajes como este, por favor haz clic en el siguiente link:<br><a href='http://www.cehcom/unsubscribe.php?type=2' target='_blank'>http://www.fyocom/unsubscribe.php?type=2</a><br> <br></pre> </div> </div> </div> </body> </html> [View Less]

8 10

[Twisted-Python] [ANN] txZMQ released
by Andrey Smirnov July 21, 2014

July 21, 2014

Hi! I would like to announce txZMQ, ZeroMQ bindings for Twisted. txZMQ is based on pyzmq and requires recent ØMQ version (>=2.1). txZMQ uses ØMQ APIs to get file descriptor that is used to signal pending actions from ØMQ library IO thread running in separate thread. txZMQ should be usable with any Twisted reactor. ØMQ is: * The socket library that acts as a concurrency framework. * Carries messages across inproc, IPC, TCP, and multicast. * Connect N-to-N via fanout, pubsub, pipeline,… [View More]

8 11

[Twisted-Python] txThings - simple library for CoAP protocol
by Maciej Wasilak Nov. 25, 2013

Nov. 25, 2013

Hello everyone, I would like to announce the first release of txThings. It is a simple library for Constrained Application Protocol (CoAP). CoAP is a relatively new protocol designed for "Internet of Things" and M2M communications. txThings currently implements a subset of CoAP features: - standard messaging based on draft-ietf-core-coap-13 (no proxying support yet) - blockwise transfers based on draft-ietf-core-block-12 - limited suport for RFC6690 Core Link Format (for servers only) I hope … [View More]

5 10

[Twisted-Python] AMP Argument.toBox's proto argument is a locator, not the proto?
by Laurens Van Houtven Nov. 20, 2013

Nov. 20, 2013

Hi everyone, I think I've hit one of those cases where AMP really seems to want everything (locator, receiver, sender) to be an instance of t.p.amp.AMP :-( I've written some code that tries to multiplex stream transports over AMP: https://github.com/lvh/txampext/blob/multiplexing/txampext/multiplexing.py The repo contains an example server and client, which demonstrate the issue: https://github.com/lvh/txampext/blob/multiplexing/docs/examples/multiplexin… https://github.com/lvh/txampext/… [View More]

2 6

[Twisted-Python] Clean pb solution for two-way object sync?
by Daniel Sank Oct. 25, 2013

Oct. 25, 2013

(Apologies for double send but I forgot the subject line) Dear Twisted users, I recently found myself implementing a design pattern that I think twisted.pb was specifically designed to address. I think I'm not using pb correctly so I'd like advice. This is a somewhat longish post because I need to describe the problem I'm trying to solve. I have done internet searches on Stack Overflow and this list but have not found the answer to my question. If I've missed something kindly direct me to … [View More]the appropriate reference. I want to implement something functionally equivalent to a network chess game. I first consider how I would do this on a single computer with no network (maybe this is bad thinking). Each piece in the game is represented by an instance of class Agent. Each agent has a .graphics attribute which is an instance of a class from a GUI toolkit library or equivalent. Whenever an agent in the game needs to do something there will be business logic executed by the game objects proper (ie the agents) which will invoke methods on the .graphics objects to update the screen. This sort of structure seems natural as it allows easy integration of drag/drop, mouse click detection etc. It also nicely separates the real business logic from the GUI. Now I want to run over the network. The question is how should I set up references between the client and server objects? Surely the server will maintain a set of objects representing the pieces in the game. It seems reasonable that each user's program will have a corresponding set of objects (with .graphics attributes). The issue is, what do we mean by "corresponding" and how do these objects talk to one another? Following is my idea so far: Each instance of AgentClient has a .server attribute which is a remote reference to an instance of AgentServer, and each instance of AgentServer has a .clients attribute which is a list of remote references to instances of AgentClient. class AgentServer(pb.referenceable): def remote_move(self, targetSquare): """Handle move request from client""" if self.thisMoveIsLegal(targetSquare): self.position = targetSquare for client in self.clients: client.callRemote("move", targetSquare) def thisMoveIsLegal(self, targetSquare): <check that this is a legal move> class AgentClient(pb.referenceable): def requestMove(self, targetSquare): """Tell server we'd like to move""" self.server.callRemote("move", targetSquare) def remote_move(self, targetSquare): """Server told us we moved""" self.position = targetSquare self.graphics.setNewPosition(targetSquare) This isn't THAT bad. The client's requestMove is thin and unecessary (I put it there for illustration). Still I need to have two separate classes with corresponding methods to handle moving the piece. This seems like the kind of thing I could twisted.pb to solve more cleanly if I only would look in the right place. This problem gets even worse when I think about how to birth new in-game objects. It would have to look like this: class PlayerServer(pb.referenceable): def newAgent(self, asker): """Client told us it wants a new Agent""" if self.thisIsLegal(): a = AgentServer() self.agents.append(a) for client in self.clients: d = client.callRemote("newAgent", a) d.addCallback(lambda obj: a.clients.append(obj)) class PlayerClient(bp.referenceable): def requestNewAgent(self): """Tell the server we want to spawn a new Agent""" self.server.callRemote("newAgent", self) def newAgent(self, serverObj): a = AgentClient() self.agents.append(a) a.server = serverObj return a This just looks wrong. Any advice? Thank you in advance for your help. Regards, Daniel Sank [View Less]

5 9

[Twisted-Python] regarding xml elements
by Raj kumar Oct. 2, 2013

Oct. 2, 2013

Hi, I have an xml file in my application, I have created an element using Example goes like this......... document.createElement("abc") and i appeneded it by using append() method. But how i can reflect this change to my xml file? and one more thing is i want to create element with some other parameters.... like............. <abc m=" " n=" "> </abc> and i have m and n values as strings with me. can anybody help me to create this element and write it to the existing xml … [View More]

9 14

[Twisted-Python] Twisted Sprint Report (2013-09-23)
by Richard Wall Oct. 2, 2013

Oct. 2, 2013

Twisted Sprint Report (2013-09-23) * Venue PyconUK 2013, Coventry, England * Attendees * Lasse Bromose * Stephen Evans * Holger Kraus * Lukasz Prasol * Christophe Reche * Richard Wall * Summary Five Twisted enthusiasts were introduced to the Twisted development process. We closed 2 tickets, made some progress on 2 others and improved some of the development process documentation. * Details ** http://tm.tl/6406 Christophe, Lukasz and Holger helped improve the Trial … [View More]

6 13

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com Sept. 29, 2013

Sept. 29, 2013

1 0

[Twisted-Python] (no subject)
by Daniel Sank Sept. 26, 2013

Sept. 26, 2013

Dear Twisted users, I recently found myself implementing a design pattern that I think twisted.pb was specifically designed to address. I think I'm not using pb correctly so I'd like advice. This is a somewhat longish post because I need to describe the problem I'm trying to solve. I have done internet searches on Stack Overflow and this list but have not found the answer to my question. If I've missed something kindly direct me to the appropriate reference. I want to implement something … [View More]functionally equivalent to a network chess game. I first consider how I would do this on a single computer with no network (maybe this is bad thinking). Each piece in the game is represented by an instance of class Agent. Each agent has a .graphics attribute which is an instance of a class from a GUI toolkit library or equivalent. Whenever an agent in the game needs to do something there will be business logic executed by the game objects proper (ie the agents) which will invoke methods on the .graphics objects to update the screen. This sort of structure seems natural as it allows easy integration of drag/drop, mouse click detection etc. It also nicely separates the real business logic from the GUI. Now I want to run over the network. The question is how should I set up references between the client and server objects? Surely the server will maintain a set of objects representing the pieces in the game. It seems reasonable that each user's program will have a corresponding set of objects (with .graphics attributes). The issue is, what do we mean by "corresponding" and how do these objects talk to one another? Following is my idea so far: Each instance of AgentClient has a .server attribute which is a remote reference to an instance of AgentServer, and each instance of AgentServer has a .clients attribute which is a list of remote references to instances of AgentClient. class AgentServer(pb.referenceable): def remote_move(self, targetSquare): """Handle move request from client""" if self.thisMoveIsLegal(targetSquare): self.position = targetSquare for client in self.clients: client.callRemote("move", targetSquare) def thisMoveIsLegal(self, targetSquare): <check that this is a legal move> class AgentClient(pb.referenceable): def requestMove(self, targetSquare): """Tell server we'd like to move""" self.server.callRemote("move", targetSquare) def remote_move(self, targetSquare): """Server told us we moved""" self.position = targetSquare self.graphics.setNewPosition(targetSquare) This isn't THAT bad. The client's requestMove is thin and unecessary (I put it there for illustration). Still I need to have two separate classes with corresponding methods to handle moving the piece. This seems like the kind of thing I could twisted.pb to solve more cleanly if I only would look in the right place. This problem gets even worse when I think about how to birth new in-game objects. It would have to look like this: class PlayerServer(pb.referenceable): def newAgent(self, asker): """Client told us it wants a new Agent""" if self.thisIsLegal(): a = AgentServer() self.agents.append(a) for client in self.clients: d = client.callRemote("newAgent", a) d.addCallback(lambda obj: a.clients.append(obj)) class PlayerClient(bp.referenceable): def requestNewAgent(self): """Tell the server we want to spawn a new Agent""" self.server.callRemote("newAgent", self) def newAgent(self, serverObj): a = AgentClient() self.agents.append(a) a.server = serverObj return a This just looks wrong. Any advice? Thank you in advance for your help. Regards, Daniel Sank [View Less]

1 0

[Twisted-Python] Running unit tests without trial?
by Russell E. Owen Sept. 25, 2013

Sept. 25, 2013

Is it possible to run twisted.trial unit tests using python instead of trial, i.e.: "python mytest.py" instead of "trial mytest.py"? I'm hoping there is some simple magic I can put into the unit test itself to make this work. Perhaps something in if __name__ == "__main__": ...? to make it start up the reactor and run it correctly. I ask because I'm using a build environment that runs all unit tests this way. It does the sniffing out and the saving of logs, but it insists on running .… [View More]

2 2

Re: [Twisted-Python] Running unit tests without trial?
by Julian Berman Sept. 25, 2013

Sept. 25, 2013

On Wed, 25 Sep 2013 18:45:44 -0000 exarkun(a)twistedmatrix.com wrote: > On 06:15 pm, rowen(a)uw.edu wrote: > >Is it possible to run twisted.trial unit tests using python instead of > >trial, i.e.: "python mytest.py" instead of "trial mytest.py"? > > Sure. Here's the worst case answer (contents of mytest.py): > > import os > os.system("trial myrealtests.py") There is also http://twistedmatrix.com/trac/ticket/4797 Cheers, Julian

1 0

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com Sept. 22, 2013

Sept. 22, 2013

1 0

[Twisted-Python] How to disconnect an HTTP connection and notify the far end
by Bob Novas Sept. 20, 2013

Sept. 20, 2013

I've got a question on how to explicitly disconnect a connection from the client side so that the server side knows that the connection has been disconnected. I'd be happy if this worked even with no guarantees, i.e., only when the client and server were in fact well-connected. It's just an optimization to allow the server to cleanup. I've got an HTTP client that uses HTTPConnectionPool to get an Agent, gets a Request from the Agent, and sends the Request to a WebServer on a linux box. … [View More]

2 1

[Twisted-Python] Cancelling a pb callRemote
by Phil Mayers Sept. 19, 2013

Sept. 19, 2013

Is there any support, or any interest in / way to add support for deferred cancellation in pb? Specifically I'd like do have something like: class blah(pb...): def remote_somelongtask(self, args): ... taskid = somefunc() d = defer.Deferred(lambda : canceltask(taskid)) return d ...and on the client: d = callRemote('somelongtask', args) ... # now we no longer need it d.cancel() ...and have the cancel the server-side task.

6 11

[Twisted-Python] Twisted at PyConUK 2013
by Richard Wall Sept. 19, 2013

Sept. 19, 2013

Hello everyone, I'm giving a talk about Twisted and Twisted Names at PyConUK this year. The schedule hasn't been fixed yet, but it looks like it'll be this Friday 20 September at 1530. If you're going to PyConUK I'd welcome your support, especially with fielding any tricky audience questions. ;-) * http://pyconuk.net/Schedule I'm also hoping to organise a Twisted Sprint, so if you're still around on Monday come and find me. * http://pyconuk.net/Sprints -RichardW. PS. I'd love to merge … [View More]

4 6

[Twisted-Python] run python application with twistd -y ifinger.tac, error occurs. please help to check
by 吴志高 Sept. 18, 2013

Sept. 18, 2013

Experts: 您好！ my ifinger.tac file content like following: fromtwisted.applicationimportinternet, servicefromtwisted.internetimportprotocol, reactor, deferfromtwisted.protocolsimportbasicclassFingerProtocol(basic.LineReceiver): deflineReceived(self, user): d = self.factory.getUser(user) defonError(err): return'Internal error in server'd.addErrback(onError) defwriteResponse(message): self.transport.write(message + '\r\n') self.… [View More]

3 5

[Twisted-Python] infrastructure hosting confusion / cleanup
by Glyph Sept. 18, 2013

Sept. 18, 2013

Pages like this one: <http://buildbot.twistedmatrix.com/builders/pyflakes/builds/1008> information about the source code being built in the form of a git revision. As long as we're still using Subversion for our upstream VCS, it would be desirable to also have a Subversion revision number. I wanted to request this, but even I have lost track, at this point, of where to file bugs for things like this. It looks like we're hosting our infrastructure projects on Github right now, which … [View More]

1 0

[Twisted-Python] logging
by Glyph Sept. 18, 2013

Sept. 18, 2013

Hello everybody. Today I'd like to talk about everyone's favorite subsystem within Twisted: logging. There are a number of problems with Twisted's logging system. The general theme of these problems is that Twisted log system was designed with some intended use-cases in mind, but its implementation was stopped halfway through and none of those use-cases were really well satisfied. At various conferences, and in person at various times, we've gotten together to express frustration at the … [View More]logging system, but I don't think that the problems with it have ever been really thoroughly written down. Wilfredo has been working on logging here: http://trac.calendarserver.org/browser/CalendarServer/trunk/twext/python/lo…. This began as an attempt to just address some issues with our own logging wrappers, but has been growing into a design that is more fully capable of replacing logging within Twisted wholesale. I hope one of us can contribute it to Twisted soon, but in the meanwhile, please feel free to provide feedback - hopefully if some people can provide a bit of informal feedback now, the formal review process can be shorter and more pleasant :). Now, back to some explanation of the current problems. The main intended use-case for Twisted's logging system is to avoid doing unnecessary work in the case where it is not required. One of the reasons we even still have our own logging system is that the stdlib logging module is notorious for doing too much work per log message, and doing it too prematurely. One aspect of this is that logging would just use the existing 'kwargs' dictionary as its message type, and not actually do any formatting; that is, string-copying, until the message was logged. On Python 1.5.2, that meant no need to allocate anything since the interpreter needed a dict for the kwargs anyway! Woohoo premature optimization! Obviously, at least on PyPy, that optimization is no longer relevant (and we don't have performance tests for logging anyway). But, I don't think we should change that because a dict is still a good object for the sort of extensibility that log messages need. But, we have never written any filtering logic, nor have we instrumented any of our existing log messages with formatting stuff. Every message with a format string just goes to the log. For a long time, there's been consensus among at least a few core Twisted developers that log messages ought to be specified in terms of a format message and several relevant keyword arguments, so that tools can extract the values of the keyword arguments without parsing ad-hoc messages or using regexes. In other words, like this: log.msg(format="Foo happened. Relevant information includes: " "bar=%(bar)s baz=%(baz)s boz=%(boz)s", bar=bar, baz=baz, boz=boz) Yet, nothing within Twisted itself does this. There's a bit of a chicken and egg problem: since we have no tools for filtering log messages based on their structured values, there's no obvious motivation to break the structured contents of a message out into those values. And since no messages break out their values into nice structured fields, there's no motivation to write filtering tools that inspect those fields. And, even if we did have filtering, we don't have a facility to easily defer work. You could, of course, just do something like this: class GenerateOnlyIfNeeded(object): def __str__(self): return doSomethingExpensiveToGenerateAString() log.msg(format="debugging: %(expensive)s", logLevel=debug, expensive=GenerateOnlyIfNeeded()) But that's an awful lot of thinking for a single log message, not to mention the temporary class and the method you needed to allocate. Such deferral of work should be easy. And, speaking of the things that one might filter on, log messages don't typically include information about what module and class they're from; or, for that matter, what object is logging them. This information should be included by default in idiomatic usage of the API, so that a filtering system can inspect them. Another reason that we - both Twisted itself and Twisted users - don't typically pass keyword arguments and a format string, is that the default argument to msg is, simply, a "message". (It also does a dumb thing where it tries to emulate the argument-passing convention of 'print' and stringify its arguments and join them with spaces; we should get rid of that.) Instead, that argument always ought to be a format string. We should also have a log writer within Twisted that preserves structure, and dumps the logs using JSON (or similar, perhaps more than one of these; AMP would be another good thing). It's also not possible to use format strings when you are writing an error log message in Twisted; instead, 'why' is treated completely differently than 'message'. The 'why' argument to 'err', which should be mandatory (what were you doing when you tried to log a message?) is optional, which means that error messages are even more inscrutable. The portions of the dictionary used by the logging system are not namespaced in any way, even by convention. Therefore it's easy for a user to conflict with the keys used by the system. If users of Twisted actually used the system as intended more pervasively, I'm pretty sure that we would end up seeing people conflict with 'time' and 'system' arguments often. Speaking of those keys: the 'time' key is unconditionally overwritten by log.msg, which means that re-publishing an event that happened previously is destructive; there's no way to track historical time. Messages logged before the logging system starts are just lost. It would be good for the initial log observer to keep a (limited-size, of course) buffer of log messages which could be dumped upon failing. This would make it easier, for example, to debug tap plugins that use the log system to report something about their state during makeService. (And, as the maintainer of a phenomenally complex makeService, I can tell you that this would definitely be helpful.) The naming of methods is bad and confusing. msg? err? Easy to type, but hard to understand. We could have equally short names that are not confusing. The contract between parts of the system is poorly specified. For example, trial -j has a hard time with log output that includes any non-bytes keys. I imagine this will only become worse when trial actually supports Python 3. And speaking of encoding, the log system is written in terms of bytes instead of in terms of unicode. Now, there's good reason to be particularly permissive of garbage data in the logging system (logging a message should never provoke an error), but at some point - probably before the data gets to user-written observers - everything should be normalized into a structure that has enough properties that the user can depend on it. On that note, when presented with unicode encoding errors, Twisted's logger will directly raise an exception back to application code, something that it will otherwise only do when presented with KeyboardInterrupt. That I just don't understand. We use old, semi-deprecated '%' formatting style. If we're going to introduce a new API, we should use PEP 3101 formatting; in addition to being new and improved instead of old and inferior, it's a lot easier to type {foo} correctly than to type %(foo)s without forgetting the s. The whole LogContext thing is poorly designed. Mea culpa; this was entirely my fault. One problem with its design was that it was somewhat poorly explained, and so its intent has not carried over years of maintenance. The idea was supposed to be that every event-source within Twisted would provide a useful system key, which would indicate what event-source object (TCP connection, listening port, timed event, UDP port) was being activated when the given message was logged. However, a lot of factors conspire to make this information less than useful. For one thing, especially in database-backed applications, or those that are careful about rate-limiting or flow-control, nothing ever happens except in response to a callFromThread or a callLater; this means that the system argument is always "-". I think that the feature this is trying to support needs to be fundamentally re-thought (and in the intervening decade I've had a lot of ideas about how it might work better). Maybe we can build on some of Chris Armstrong's recent work on Deferred debugging in tracking asynchronous context in Deferreds to help identify the real cause(s) of work being executed. OK, I think that's it for now. (NB: The implementation linked above doesn't address all of the issues I've enumerated in this message, and I don't think that it should address every single one of them before being added to Twisted; writing this one message took me long enough, but we should possibly also discuss which ones are fundamental issues with the logging system and which are features that should be considered separately.) -glyph [View Less]

12 40

[Twisted-Python] Twisted Names EDNS(0) support [Was Twisted at PyConUK 2013]
by Richard Wall Sept. 17, 2013

Sept. 17, 2013

On 17 September 2013 16:34, Phil Mayers <p.mayers(a)imperial.ac.uk> wrote: > On 17/09/13 15:29, Richard Wall wrote: > >> PS. I'd love to merge https://tm.tl/5675 before the conference, so if >> you're familiar with the DNS RFCs, I'd really appreciate a code >> review. I'm rwall on #twisted-dev and #twisted if you want to discuss >> it > > > Deep breath... I'll give this a go. Thanks Phil, I'd seen your previous work in this area and was hoping you'… [View More]

3 2

Re: [Twisted-Python] Twisted Names EDNS(0) support [Was Twisted at PyConUK 2013]
by Richard Wall Sept. 17, 2013

Sept. 17, 2013

On 17 September 2013 17:18, Richard Wall <m-lists(a)the-moon.net> wrote: > You might be interested to read the reviews of > https://twistedmatrix.com/trac/ticket/5675 where we introduced support > for parsing of OPT pseudo records. Sorry, wrong link. This is the OPT record ticket - https://twistedmatrix.com/trac/ticket/5668 And this is the EDNS plan: * https://twistedmatrix.com/trac/wiki/EDNS0 -RichardW.

1 0

[Twisted-Python] [ANN] structlog – bring context & structure to your logs without boilerplate
by Hynek Schlawack Sept. 17, 2013

Sept. 17, 2013

Hi folks, today, I’ve release the 0.2.0 of my structlog project whose ambition is no less than changing the way we log in Python. :) And since it sports dedicated support for Twisted <http://www.structlog.org/en/latest/twisted.html> (but is not limited to it, it wraps *any* logger), I’d like to introduce you to it. Basically, its premise is that events happen in a context and you want to log out both effortlessly. Nowadays logs are usually consumed by parsers anyway, so regular, … [View More]easily parsable logs are a good thing™. This is a nice example of a Twisted application showing off a bit what structlog is capable of: import sys import uuid import structlog import twisted from twisted.internet import protocol, reactor logger = structlog.getLogger() class Counter(object): i = 0 def inc(self): self.i += 1 def __repr__(self): return str(self.i) class Echo(protocol.Protocol): def connectionMade(self): self._counter = Counter() self._log = logger.new( connection_id=str(uuid.uuid4()), peer=self.transport.getPeer().host, count=self._counter, ) def dataReceived(self, data): self._counter.inc() log = self._log.bind(data=data) self.transport.write(data) log.msg('echoed data!') if __name__ == "__main__": structlog.configure( processors=[structlog.twisted.EventAdapter()], logger_factory=structlog.twisted.LoggerFactory(), ) twisted.python.log.startLogging(sys.stderr) reactor.listenTCP(1234, protocol.Factory.forProtocol(Echo)) reactor.run() It will give you an output like: 2013-09-17 17:40:23+0200 [-] Log opened. 2013-09-17 17:40:23+0200 [-] Factory starting on 1234 2013-09-17 17:40:23+0200 [-] Starting factory <twisted.internet.protocol.Factory instance at 0x108301488> 2013-09-17 17:40:28+0200 [Echo,0,127.0.0.1] peer='127.0.0.1' count=1 connection_id='4e2ee31c-b3ff-478e-ae06-7b1a492fce45' data='foo\n' event='echoed data!' 2013-09-17 17:40:33+0200 [Echo,0,127.0.0.1] peer='127.0.0.1' count=2 connection_id='4e2ee31c-b3ff-478e-ae06-7b1a492fce45' data='bar\n' event='echoed data!' 2013-09-17 17:40:44+0200 [Echo,1,127.0.0.1] peer='127.0.0.1' count=1 connection_id='3118f673-482b-471f-a206-e8f97f9a9c2c' data='qux\n' event='echoed data!' 2013-09-17 17:40:53+0200 [Echo,0,127.0.0.1] peer='127.0.0.1' count=3 connection_id='4e2ee31c-b3ff-478e-ae06-7b1a492fce45' data='twisted prevails\n' event='echoed data!' (you can find this and more examples at <http://www.structlog.org/en/latest/examples.html>) In short: - It allows you to build context by binding values to loggers. This context is just a dictionary. Once you log an event out (again, arbitrary number of key/value pairs), it gets merged with the context, processed by configurable processor chain and passed to your original logger. - Your loggers are immutable (by default infidels can use thread local storage) and you’ll get a new one on each binding. Immutable local data is awesome. - You can define processors that can mangle, filter, and format your log entries. - Configure once, then just call getLogger (which is a Twisted-friendly alias for get_logger) in regular code. - Of course there is a JSON renderer built right in – just tell log stash about it and be merry. *Please* have a look at <http://www.structlog.org/en/0.2.0-0/getting-started.html>, I don’t want to reproduce it here. :) Credit where credit is due: I picked up the idea of bound loggers from David Reid’s work on otter <https://github.com/rackerlabs/otter/tree/master/otter/log> which in turn was based on ideas by JP (I’ve been told). You can find everything you need to know at http://www.structlog.org/ – I’d be happy about any constructive feedback and even more so about contributions! Cheers, Hynek [View Less]

1 0

[Twisted-Python] Python 3: bytes vs. str in twisted.python.filepath
by Harry Bock Sept. 15, 2013

Sept. 15, 2013

Hi all, My name is Harry Bock. I'm interested in helping out porting Twisted to Python 3, and I've popped in IRC a few times to introduce myself and ask a few questions. A few developers agreed that working on trial dependencies would be a big help. In doing some porting work on trial, I stumbled upon a previous porting effort (possibly by Itamar?) for twisted.python.filepath and related modules. It seemed like the porting effort included forcing all pathname inputs to be byte strings … [View More]

5 7

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com Sept. 15, 2013

Sept. 15, 2013

1 0