Re: [Twisted-Python] Migration to Git / GitHub

2015-11-13 Thread Glyph Lefkowitz
> On Nov 13, 2015, at 6:07 PM, Jonathan Vanasco wrote: > > Two notes: > > 1. Have you considered bitbucket? I personally prefer github, but I know > some python projects like it because of mercurial support. We wrote up a proposal for the fellowship at the beginning of this year,

Re: [Twisted-Python] Migration to Git / GitHub

2015-11-13 Thread Jonathan Vanasco
Two notes: 1. Have you considered bitbucket? I personally prefer github, but I know some python projects like it because of mercurial support. 2. There are a lot of projects for transitioning trac tickets to github/bitbucket via their api. You can't transition some fields (reports, comments,

Re: [Twisted-Python] HTTP/2 and Twisted

2015-11-13 Thread Tristan Seligmann
On Thu, 12 Nov 2015 at 12:46 Cory Benfield wrote: > However, this may not work: in particular, some of the other classes in > twisted.web may know altogether too much about HTTP/1.X: in particular, if > they have the nerve to write directly to a transport we’ve got a real > problem with this appr

Re: [Twisted-Python] Streaming HTTP

2015-11-13 Thread Zooko Wilcox-O'Hearn
> What do people think of this approach? It sounds fine to me. I think this issue in Twisted is currently the blocker (or at least *one of* the blockers) for Tahoe-LAFS ticket #113, #320, and #1032. It is also a blocker for the much more ambitious Tahoe-LAFS tickets #1288 and #1851. Regards, Zo

[Twisted-Python] Streaming HTTP

2015-11-13 Thread Cory Benfield
Folks, # Problem Statement Thanks for your feedback on my HTTP/2 questions. I’ve started work implementing a spike of a HTTP/2 protocol for twisted.web. I’m aiming to have something that works in at least some cases by the end of the day. As part of my dive into twisted.web, I noticed somethin