Mailman 3 July 2017 - Twisted

[Twisted-Python] Custom log "files" with twisted.logger
by Jean-Paul Calderone July 3, 2017

July 3, 2017

Hello, I would like to be able to send events from the new logging system (twisted.logger) to a remote log collection system. If I'm using twist then it seems options for configuring this part of logging are limited. The choices appear to be logging to stdout, stdout, or a file on the filesystem. If I write my own command-line entrypoint then I can probably do whatever I want by writing a custom observer and hooking it up appropriately. I'd rather not have to do that, though. I could also go back to twistd and use --logger. But since interest in twistd appears to be on the decline, in favor of twist, I'd rather avoid that as well. It seems like the idea would be something like --logger for twist, perhaps replacing the --log-file option. If there were a way to pass some arguments that would be pretty nice as well. twist --logger myapp.something:x=y,a=b twist --logger twisted.logger.FileLogObserver.fromPath:path=/foo/bar (Actual syntax not that important to me; consistency with endpoint syntax would have some advantages; something that deals with the necessities of quoting and nesting would be better, of course. Also, I know everyone hates Twisted's plugins but they would make for a nicer UI than FQPNs here.) The first thing I'm likely to do with this is bridge twisted.logger events to Eliot. I think this will provide the most useful logs (at least *some* of the logs from Twisted will have a meaningful Eliot context, though certainly nowhere near all). Also I already have a system for configuring Eliot log destinations (which supports passing along arguments, so I can already tell Eliot where my remote log collector is with a command-line argument). What are the chances of getting support for this scenario into twist itself? Thanks, Jean-Paul

2 1

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com July 2, 2017

July 2, 2017

1 0

[Twisted-Python] pywin32 to pywincff conversion (help needed)
by Oliver Palmer July 1, 2017

July 1, 2017

All, So a long while back I volunteered to write a library to supply functions to replace pywin32 with a cffi backed implementation. Quite a bit of time has gone by since and about a year ago I closed the issue[0] where I was keeping track of the major functions, constants and structures I needed to implement to even consider replacing pywin32. With that issue closed pywincffi may be in a position where the conversion can start. Sadly however I don't have the time myself to invest in the effort because I have a couple of other projects that have shifted my priorities. If there's someone here who does have the time to invest in the conversion I'm happy to support their efforts wherever I can. [0] https://github.com/opalmer/pywincffi/issues/69 ---Oliver

2 1