Twisted 10.2.0, the third Twisted release of 2010, has emerged from the mysterious depths of Twisted Matrix Labs, as so many releases before it. Survivors of the release process - what few there were of them - have been heard to claim that this version is "awesome", "even more robust", "fun-sized" and "oven fresh".
Crossing several things that shouldn't ought to be, including the streams and the rubicon, I have assumed the triple responsibilities of feature author, project leader, *and* release manager for 10.2: with this dark and terrible power - a power which no man ought to wield alone - I have wrought a release which contains many exciting new features, including:
- A plug-in API for adding new types of endpoint descriptions. <http://tm.tl/4695>
- A new, simpler, substantially more robust CoreFoundation reactor. <http://tm.tl/1833>
- Improvements to the implementation of Deferred which should both improve performance
and fix certain runtime errors with long callback chains. <http://tm.tl/411>
- Deferred.setTimeout is (finally) gone. To quote the author of this change:
"A new era of peace has started." <http://tm.tl/1702>
- NetstringReceiver is substantially faster. <http://tm.tl/4378>
And, of course, nearly one hundred smaller bug fixes, documentation updates, and general improvements. See the NEWS file included in the release for more details.
Look upon our Twisted, ye mighty, and make your network applications event-driven: get it now, from:
... or simply install the 'Twisted' package from PyPI.
Many thanks to Christopher Armstrong, for his work on release-automation tools that made this possible; to Jonathan Lange, for thoroughly documenting the process and thereby making my ascent to the throne of release manager possible, and to Jean-Paul Calderone for his tireless maintenance of our build and test infrastructure as well as his help with the release.
Most of all, thanks to everyone who contributed a patch, reported a bug or reviewed a ticket for 10.2. Not including those already thanked, there are 41 of you, so it would be a bit tedious to go through everyone, but you know who you are and we absolutely couldn't do it without you! Thanks a ton!
On 12:24 pm, peter.westlake(a)pobox.com wrote:
>On Wed, 13 Oct 2010 17:36 +0000, exarkun(a)twistedmatrix.com wrote:
>>On 05:22 pm, peter.westlake(a)pobox.com wrote:
>> >I'm about to start looking at this. Is there any formal procedure to
>> >or shall I just put in a ticket and assign it to myself?
>>That's the formal procedure. :)
>Okay, it's in as ticket 3031. I can't see a way to assign it to
>myself, probably because it wouldn't be sensible to give full
>access to random people off the Internet!
I gave you the "contributor" role which hopefully will let you do a few
more things with tickets.
When I create sessions with
the session's uid does not survive when the server is restarted. But
this is a problem: I want my sessions to expire solely by either
closing the browser (and thus destroying the cookie) or expiry with
idle timeout, and not by a server restart (because I have implemented
a mechanism by which sessions are persistent on disk. Kinda useless if
they don't survive server restarts).
How do I achieve this kind of behavior?
Engineer : How do I do it?
Economist : How much will it cost?
Twisted Developer: But does it block?