Re: [Twisted-Python] tubes now a separate project

> On Dec 29, 2014, at 12:46 PM, Glyph Lefkowitz wrote: > > >> On Dec 27, 2014, at 9:46 AM, exar...@twistedmatrix.com >> wrote: >> >> On 12:13 am, gl...@twistedmatrix.com wrote: >>> Apropos of recent discussion, I have moved t

Re: [Twisted-Python] tubes now a separate project

> On Dec 27, 2014, at 9:46 AM, exar...@twistedmatrix.com wrote: > > On 12:13 am, gl...@twistedmatrix.com wrote: >> Apropos of recent discussion, I have moved tubes to >> github . >> >> I've filed some issues there and plan to file more. P

Re: [Twisted-Python] tubes now a separate project

On 12:13 am, gl...@twistedmatrix.com wrote: Apropos of recent discussion, I have moved tubes to github . I've filed some issues there and plan to file more. Please start sending pull requests if you'd like to work on it with me. Cool!

Re: [Twisted-Python] tubes now a separate project

> On Dec 26, 2014, at 4:13 PM, Glyph Lefkowitz wrote: > > Apropos of recent discussion, I have moved tubes to > github . > > I've filed some issues there and plan to file more. Please start sending > pull requests if you'd like to work

Re: [Twisted-Python] Tubes!

A helix is twisted but isn't necessarily a tube. Macaroni on the other hand... On Thu, Dec 11, 2014 at 4:09 PM, Christopher Armstrong < ra...@twistedmatrix.com> wrote: > > > > On Dec 11, 2014, at 6:00 PM, Donald Stufft wrote: > > > > > >> On Dec 11, 2014, at 6:55 PM, Itamar Turner-Trauring < > it

Re: [Twisted-Python] Tubes!

> On Dec 11, 2014, at 6:00 PM, Donald Stufft wrote: > > >> On Dec 11, 2014, at 6:55 PM, Itamar Turner-Trauring >> wrote: >> >> I would suggest including the Twisted support inside tubes as a first pass, >> restricted to a module (e.g. tubes.helical). Less overhead and as long as >> it's op

Re: [Twisted-Python] Tubes!

> On Dec 11, 2014, at 6:55 PM, Itamar Turner-Trauring > wrote: > > I would suggest including the Twisted support inside tubes as a first pass, > restricted to a module (e.g. tubes.helical). Less overhead and as long as > it's optional it's not preventing anyone from using tubes with other >

Re: [Twisted-Python] Tubes!

I would suggest including the Twisted support inside tubes as a first pass, restricted to a module (e.g. tubes.helical). Less overhead and as long as it's optional it's not preventing anyone from using tubes with other frameworks. Otherwise, +100. _

Re: [Twisted-Python] Tubes!

> On Jul 10, 2014, at 21:32, exar...@twistedmatrix.com wrote: > > Tubes have been largely Glyph's effort (though a lot of people have > contributed in one way or another). And a large effort it's been. > Development is proceeding in a Twisted branch and comes to over three > thousand lines of

Re: [Twisted-Python] Tubes!

On Thu, Jul 10, 2014 at 10:37 PM, Glyph Lefkowitz wrote: > While I currently believe that Tubes's API has firmed up and its current API > is suitable for general purpose use, I have believed that at various points > in the past as well when it was completely wrong. This sentiment is very > much o

Re: [Twisted-Python] Tubes!

Glyph Lefkowitz writes: While I currently believe that Tubes's API has firmed up and its current API is suitable for general purpose use, I have believed that at various points in the past as well when it was completely wrong. This sentiment is very much of the "this time for sure!" variety,

Re: [Twisted-Python] Tubes!

> Specifically, I think it would be beneficial to set up a tubes project on > Github > under the Twisted organization and try for a release in the very near future. > > I think this has several advantages over the status quo: +1 for splitting into a separate project. even if Tubes would be cons

Re: [Twisted-Python] Tubes! (package metadata and version constraints)

On Jul 10, 2014, at 5:23 PM, exar...@twistedmatrix.com wrote: > On 10 Jul, 08:37 pm, gl...@twistedmatrix.com wrote: >> >> On Jul 10, 2014, at 12:32 PM, exar...@twistedmatrix.com wrote: >>> 2) As a separate Python package, the logistics of actually using tubes are >>> simpler (just consider how

Re: [Twisted-Python] Tubes! (package metadata and version constraints)

On 10 Jul, 08:37 pm, gl...@twistedmatrix.com wrote: On Jul 10, 2014, at 12:32 PM, exar...@twistedmatrix.com wrote: 2) As a separate Python package, the logistics of actually using tubes are simpler (just consider how you might declare a dependency on a branch of Twisted - keeping in mind you m

Re: [Twisted-Python] Tubes!

Hmm, perhaps —pre shouldn’t be allowed in config files :V On Jul 10, 2014, at 5:19 PM, Glyph Lefkowitz wrote: > > On Jul 10, 2014, at 1:47 PM, Christopher Armstrong > wrote: > >> For what it’s worth, if you add an “a%n” to the end of a version, pip won’t >> install it unless you specify the

Re: [Twisted-Python] Tubes!

On Jul 10, 2014, at 1:47 PM, Christopher Armstrong wrote: > For what it’s worth, if you add an “a%n” to the end of a version, pip won’t > install it unless you specify the version exactly. e.g., “tubes” version > “0.1a1” won’t be found if you type “pip install tubes”, only “pip install > tub

Re: [Twisted-Python] Tubes!

On July 10, 2014 at 3:40:26 PM, Glyph Lefkowitz (gl...@twistedmatrix.com) wrote: On Jul 10, 2014, at 12:32 PM, exar...@twistedmatrix.com wrote: 2) As a separate Python package, the logistics of actually using tubes are simpler (just consider how you might declare a dependency on a branch of

Re: [Twisted-Python] Tubes!

On Jul 10, 2014, at 12:32 PM, exar...@twistedmatrix.com wrote: > Hello all, > > Some of you may have heard rumors of some work in progress on a replacement > for Twisted's IConsumer/IProducer interfaces. > > Tubes have been largely Glyph's effort (though a lot of people have > contributed in