Mailman 3 April 2012 - Twisted

[Twisted-Python] txws.py websocket and Python 2.4
by matusis＠yahoo.com April 12, 2012

April 12, 2012

I do not quite know the most recent status of txws.py, whether it is being merged to Twisted or not. But I noticed that it has it has two incompatibilities with Python 2.4: 1. from hashlib import md5, sha1 2. protocol = "wss" if self.isSecure() else "ws" After fixing those, it works on 2.4. Would it make sense to make that change on github?

1 0

[Twisted-Python] IPv6 Support for Client side
by Peng Xiao -X (penxiao - Digital China at Cisco) April 11, 2012

April 11, 2012

Hi experts, The release of Twisted 12.0 support IPV6 on the server side, I want to know that when it will support IPv6 on the client side. Thanks a lot Best Regards, Xiao Peng

2 1

[Twisted-Python] question : SerialService and an autostart application of autologin user, strange behaviour
by bino oetomo April 10, 2012

April 10, 2012

Dear All .. My system is an ubuntu box with openbox and Slim. in my tac file with a SerialService, I have this line serial = SerialPort(ArduinoReceiver(), '/dev/arduino', reactor,baudrate=4800) This tac file always run well when I start it manualy from xterm. I call it using an sh script : --> startcore.sh & #!/bin/bash twistd -ny /opt/sikat/scripts/core11.tac -l /opt/sikat/scripts/core11.log --pidfile /opt/sikat/scripts/core11.pid Next ... I try to call that script from my openbox autostart.sh (/home/sikat/.config/autostart.sh) : /opt/sikat/scripts/startcore.sh & /opt/sikat/bin/navit & This way I want that whenever the system is booted, 'sikat' is autologed in by slim, and my twistd tac script is started by openbox's autostart THe result is : 1. twistd tac file is started, 2. No error log complaining about serial port, but 3. Anything send by my arduino looks like did not received by TAC script. Kindly please tell me how to (what to look for to) fix this problem Sincerely -bino-

1 0

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com April 8, 2012

April 8, 2012

1 0

[Twisted-Python] question : redis and twisteD application service framework
by bino oetomo April 4, 2012

April 4, 2012

Dear all Currently I use wokkel to bridge SerialService to my Pub/Sub system (currently based on Jabber XMPP) my co-worker is PHP guys, so it's hard to get access to XMPP from PHP. he told me about Redis, and I found txredis and TxRedisapi I want my application basically : 1. Send whatever received via serial port to redis pubsub system, and 2. Send whatever received via redis subscribe to serial port. Is there any example on using redis with 'twisteD application service framework' so that I can run it using something like : twistd -ny ./myapp.tac -l ./myapp.log --pidfile myapp.pid Sincerely -bino-

1 0

[Twisted-Python] Question : Listen to GPSD
by bino oetomo April 4, 2012

April 4, 2012

Dear all. Recently, for my MDT project I use 2 twisted script. one for the core process (XMPP, LineReceiver, SerialService), and one for displaying msg (twisted with WxPython) I need 2 of them .. since I cannot combine them in single script. I Only familiar with 'service.Application' method. Know I replace twisted+wxpython with Navit + dbus With this method, I can display gps-things and display mysg using libnotify. So .. currently only one twisted script needed. The problem is : Navit use GPSD GPSD will takeover my 'gps-port'. This way, my twisted script can not listen to my gps-port anymore. My question is : Is there any way to make my twisted script to *listen* to GPSD ? Sincerely -bino-

1 0

[Twisted-Python] Virtual Manager Vacancy
by twisted-python＠twistedmatrix.com April 3, 2012

April 3, 2012

I would like to take this time to welcome you to our hiring process and give you a brief synopsis of the position's benefits and requirements. If you are taking a career break, are on a maternity leave, recently retired or simply looking for some part-time job, this position is for you. Occupation: Flexible schedule 2 to 8 hours per day. We can guarantee a minimum 20 hrs/week occupation Salary: Starting salary is 2000 EUR per month plus commission, paid every month. Business hours: 9:00 AM to 5:00 PM, MON-FRI, 9:00 AM to 1:00 PM SAT or part time (Europe time). Region: Europe. Please note that there are no startup fees or deposits to start working for us. To request an application form, schedule your interview and receive more information about this position please reply to Ilene(a)eureseuropa.com,with your personal identification number for this position IDNO: 6369

1 0

[Twisted-Python] Twisted is participating in Google's Summer of Code, and Outreach Program for Women
by Itamar Turner-Trauring April 1, 2012

April 1, 2012

If you're a student (or know a student) interested in a paid summer internship working on Twisted, please get in touch with me. We are also sponsoring one paid internship in partnership with Gnome's Outreach Program for Women, which unlike GSoC is not restricted to students. The deadline for both is coming up this Friday. More details: http://twistedmatrix.com/trac/wiki/GoogleSOC http://twistedmatrix.com/trac/wiki/WomenOutreach2012

1 0

[Twisted-Python] Weekly Bug Summary
by exarkun＠twistedmatrix.com April 1, 2012

April 1, 2012

1 0

[Twisted-Python] the good, the log, and the ugly
by Glyph April 1, 2012

April 1, 2012

Right now, we have a pretty bad logging idiom. All over Twisted, you'll find stuff like this: log.msg("twistd %s (%s %s) starting up." % (copyright.version, sys.executable, runtime.shortPythonVersion())) ... log.msg("Loading %s..." % filename) ... log.msg("Received unhandled keyID: %r" % (keyID,)) In other words, log messages that take structured information, but then smash it into a not-particularly-distinctive string and spit it out into a line-delimited file. The Twisted log system has, from its very beginning, supported a better style of formatting, which is: log.msg(format="twistd %(version)s (%(executable)s %(short)s) starting up.", version=copyright.version, executable=sys.executable, short=runtime.shortPythonVersion())) ... log.msg(format="Loading %(filename)s...", filename=filename) ... log.msg(format="Received unhandled keyID: %(keyID)r", keyID=keyID) There are lots of other features which this style of logging could support, as well, with relatively minor tweaks, such as trivial enhancements like: def logger(module, audience, importance): def logIt(**kw): log.msg(module=module, audience=audience, importance=importance, **kw) return logIt ... info = logger(__name__, ADMIN, NORMAL) bugreport = logger(__name__, DEVEL, HIGH) debug = logger(__name__, DEVEL, LOW) ... info(format="twistd %(version)s (%(executable)s %(short)s) starting up.", version=copyright.version, executable=sys.executable, short=runtime.shortPythonVersion())) This would then allow us to build systems which internally filter messages, avoid expensive string formatting and copying when it's not necessary, tune logging to different levels for different parts of the package hierarchy, and have intelligent real-time log analysis that inspects the objects being logged without having to apply regexes or other static-string-inspection methods to figure out which messages are interesting. Calendar Server implements some of these features for its logging system, and they've been very useful there. Various Divmod projects have implemented run-time statistics tracking via that Twisted logging system, and that worked pretty well too. It would be good to start taking advantage of the good parts of Twisted's logging system within Twisted itself. Doing this in a consistent way would also open up the possibility of localizing our log messages, which is currently not really plausible. And also, of logging in a format which lost less information; for example, instead of actually doing textToEventDict, simply dumping a simplified form of the event dict itself to some structured format that could be reliably parsed – something like JSON – for easier parsing and analysis later. However, in order to be able to take advantage of these features when they're added, we need to start avoiding premature string formatting everywhere that we can today. If you're writing log messages within twisted (or within a twisted application or library) please adopt the format=, x=, y= style of logging messages so that log observers can actually see into the objects being logged and do interesting things with them. We should also file some tickets about improving the documentation to indicate this style, for writing a new interface to logging which mandates this style, and for adding layers on top of that to provide more useful functionality like the aforementioned per-module or per-audience filtering. I have long despaired of filing such tickets because they each seem like boil-the-ocean tasks, changing every single call-site of log.msg (there are more than 500 as of today, just in Twisted itself, and thousands more in other applications I'm sure). I'm going to try to get started on record my desired behavior for logging as tickets soon though, so Twisted can at least have some really good logging tools eventually. -glyph

3 6