Mailman 3 May 2014 - Twisted

[Twisted-Python] Log level using Twistd
by Juan Antonio Ibañez Santorum May 4, 2014

May 4, 2014

Hello, I am trying to modify loglevel withou result. I configure my app logging inside the tac file as: logging.basicConfig(level=logging.ERROR, format="%(asctime)s --- %(name)s - %(levelname)s - %(message)s") logfile = DailyLogFile("gdumper.log", "/var/log") application.setComponent(ILogObserver, FileLogObserver(logfile).emit) logging.basicConfig call seems do not apply as I get both log.msg and log.err messages into the log. Is there any other way to set up log level? Regards

2 2

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com May 4, 2014

May 4, 2014

1 0

[Twisted-Python] Some comments regarding #5190 - ``RFC 6125 ("Service Identity") implementation´´
by exarkun＠twistedmatrix.com May 3, 2014

May 3, 2014

Hello, I've just noticed that the changeset for #5190 included some untested code. Specifically, there are no tests for the code which detects missing dependencies and emits warnings about them. I'd previously noticed that this code was broken but hadn't realized this was because it was untested. I don't think there's any disagreement whatsoever over Twisted's testing requirements. All code must have full line and branch coverage (as reported by the coverage.py tool). Developers, please write tests for all of your code (and please learn to do test-driven development - it will make this task easier, I promise). Reviewers, please don't accept proposed changes that include untested code. Thanks, Jean-Paul

3 3

[Twisted-Python] adding endpoint plugins
by David Stainton May 2, 2014

May 2, 2014

Greetings, I wrote a simple IStreamClientEndpointStringParser for using the SOCKS5ClientEndpoint with Tor: https://gist.github.com/david415/26a4ed59078d2e27376f I modified a txsocksx code example for testing the new endpoint descriptor: https://gist.github.com/david415/7c6040117319cc3b0230 ...but I am not sure how to "register" it such that calls to clientFromString can return this endpoint when the descriptor prefix matches. This doc: https://twistedmatrix.com/documents/13.2.0/api/twisted.internet.interfaces.… mentions placing the plugin in the twisted.plugins package... however this doc: http://twistedsphinx.funsize.net/projects/core/howto/plugin.html suggests that I can also set the PYTHONPATH to a directory: """if a directory which has been added to sys.path (typically by adding it to the PYTHONPATH environment variable) contains a directory named twisted/plugins/ , each .py file in that directory will be loaded as a source of plugins.""" I'm using twisted 13.2.0 in a virtualenv... and I've tried setting PYTHONPATH to a "twisted/plugins" directory no avail. I must be doing something wrong here but after scouring the docs and twisted source code... I'm just not sure. This effort is part of solving for Tahoe-LAFS trac ticket 517: "make tahoe Tor- and I2P-friendly" https://tahoe-lafs.org/trac/tahoe-lafs/ticket/517 Thanks to Glyph and JP's help I was able to write a foolscap client side patch to use twisted endpoints. See foolscap trac ticket 203: http://foolscap.lothar.com/trac/ticket/203#comment:36 str4d has already written the foolscap server side endpoint patch... Therefore it seems to me the next steps are to create parsers for endpoints we are interested in supporting... and get Tahoe-LAFS to register them so that serverFromString and clientFromString will return the expected endpoint objects. Cheers! David

6 7

[Twisted-Python] pb objects unexpectedly change identity
by Daniel Sank May 2, 2014

May 2, 2014

Dear twisted users, I think I have found some surprising behavior in perspective broker. I define a subclass of pb.RemoteCache which has a method managed by a descriptor. The descriptor keeps track of the instances it manages in a set. When the RemoteCache is first received by the client, it accesses the descriptor-ified method inside setCopyableState. At that time the RemoteCache's id is a certain value X. Then later when the RemoteCache is notified of a change by the server side Cacheable, it again accesses the descriptor-ified method, but at this time it's id is Y, and Y!=X. I attach to this post a simple working example which displays the behavior described above. To run, first run server.py and then run client.py. You will see a little bit of output, the most important part being === Client received RemoteCache: id=45952496 Asking server to update TD 45921680 (test.RemoteCache.add) accessed by <test.RemoteCache instance at 2BD2DC8>: id=45952456 RemoteCache id=45952496 === To understand the details of the output please see descriptor.py. The id of the RemoteCache is first reported as 45952496 when the client receives it. Then, when the descriptor is accessed, the id of the accessing instance is reported as 45952456, which is different. Then, when in the last line we print out the id of the RemoteCache we're back to 45952496. Is there some reason that a RemoteCache's id can change during its life time? -- Daniel Sank Department of Physics Broida Hall University of California Santa Barbara, CA 93117 (805)893-3899

1 2

[Twisted-Python] Twisted 14.0.0pre3 Announcement
by HawkOwl May 1, 2014

May 1, 2014

Hi everyone, here’s a new Twisted 14.0 prerelease for you! Tarballs for this prerelease can be found at <http://twistedmatrix.com/Releases/pre/14.0.0pre3>, with the changelog at <http://twistedmatrix.com/Releases/pre/14.0.0pre3/NEWS.txt>. Changes from the previous prerelease include: - Making Twisted Agent do HTTPS hostname verification. For more information and a full list of changes, check the NEWS.txt file. Please download the tarballs and test them with your applications, so we can make sure we’re all ready for release! -hawkowl

6 15