[Twisted-Python] Twisted 15.4 was the last release to support Python 2.6; or: a HawkOwl Can't Words Situation

Hi everyone! It's been brought to my attention that I misworded something in the release notes and it slipped through the cracks. In the NEWS I said: > This is the last Twisted release where Python 2.6 is supported, on any > platform. However, I meant that this is the first Twisted release to

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

On 5 December 2015 at 19:31, Tom Prince wrote: > > Amber commented that using milestones for such a thing is not a good idea > > and that we should use tags like: landed-in-15.5, landed-for-15.5 ... and > > keep milestones like Python-3 unchanged. > > I think rather than having a tag, it would ma

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

Glyph Lefkowitz writes: > I frequently answer stack overflow questions where I want to say what release > of Twisted a particular bug was fixed in, and it's unfortunately hard to > discover. The attached script should get most of the versions for tickets. There are a handful of tickets that get

Re: [Twisted-Python] incompatible change - need revert before release

Glyph Lefkowitz writes: > If it's been in a release, then there's probably nothing to do. It's > a shame that this went out, but once a breakage like this has happened > we have to live with it because otherwise, as you say, we'd be > breaking compatibility for the people that already upgraded.

Re: [Twisted-Python] Suggested plan for GitHub migration

Glyph Lefkowitz writes: >> Probably would be a good idea to have a list of such changes *before* the >> migration. > > Yes. Everything should be written up and reviewed beforehand, and There has been a lot of words written talking about coming up with a plan for the migration, but I have yet t

Re: [Twisted-Python] Attaching the release number to a closed/merged ticket

> Amber commented that using milestones for such a thing is not a good idea > and that we should use tags like: landed-in-15.5, landed-for-15.5 ... and > keep milestones like Python-3 unchanged. I think rather than having a tag, it would make more sense to have a custom field (http://trac.edgewall

Re: [Twisted-Python] incompatible change - need revert before release

Glyph Lefkowitz writes: > Tom Prince discovered a regression on > https://twistedmatrix.com/trac/ticket/7016#comment:14 > - I think that this > was introduced after 15.4, so it needs to be rolled back (or fixed, if > someone can get to i

Re: [Twisted-Python] Streaming HTTP

> When the object receiving the request is ready to send a response, it > calls…something (sendResponse?) and provides an object implementing a server > IResponse. The code in the H2Stream/H2Connection sends the headers, then > calls deliverBody on the IResponse, passing H2Connection (again via

Re: [Twisted-Python] Streaming HTTP

After having written the following comments, I realized that my thoughts are only about the high-level interface of Site/Resource. I think those are the interfaces most users care about, so what it makes most sense to think deeply about having a painless transiftion for. I suspect that if people ar