On 8 May 2014, at 5:40, Glyph Lefkowitz wrote:
>
> On May 7, 2014, at 7:07 AM, HawkOwl wrote:
>
>> Hi everyone,
>
> Hi HawkOwl,
>
>> I’m sure that some of you have been following the past seven or so weeks of
>> Twisted 14.0 release shenanigans, and this email hopes to explain what went
>
On May 7, 2014, at 7:42 AM, Itamar Turner-Trauring wrote:
> A diff between the 14.0.0pre5 branch and trunk suggests merging it into trunk
> would do bad things, so I'm not sure it's releasable as is... This may be
> operator error on my part though.
>
This doesn't look significant.
A squash m
On May 7, 2014, at 7:07 AM, HawkOwl wrote:
> Hi everyone,
Hi HawkOwl,
> I’m sure that some of you have been following the past seven or so weeks of
> Twisted 14.0 release shenanigans, and this email hopes to explain what went
> wrong,
Given that there does not appear to be a 14.0 final, sho
Hi Exarkun,
Thanks for the quick response. I should have specified those things
immediately.
I manually merged the UDP ipv6 branch in the trunk somewhere in august and
used that one, the version number is reported as [twisted, version 13.1.0].
The platform is always centos though the centos versio
A diff between the 14.0.0pre5 branch and trunk suggests merging it into
trunk would do bad things, so I'm not sure it's releasable as is... This
may be operator error on my part though. ___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
h
On 7 May 2014, at 16:07, HawkOwl wrote:
> 2 - Some work, medium risk - Release 14.0.0pre5 as 14.0 final,
I’m +1 on this one. The pre5 has been widely tested and the only real issues
are some embarrassing but inconsequential typos. Let’s get this out before we
introduce *real* problems.
> and
Hi!
First of all, thank you so much for working on this. Secondly, provided we
don't find any regressions in pre5, option 2 seems the least footgunny to
me :)
hth
lvh
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatr
On 01:47 pm, killia...@gmail.com wrote:
Hello everybody,
I sometimes see the following error logged by a twisted application, it
only happens sporadically and I cannot even reproduce when trying to
re-execute the exact sequence of those failures. So giving an SSCCE is
quite impossible for now (s
Hi everyone,
I’m sure that some of you have been following the past seven or so weeks of
Twisted 14.0 release shenanigans, and this email hopes to explain what went
wrong, what we can do better next time, and where we can go from here.
Problem 1: Twisted 14.0.0pre1 had a regression. This was no
Hello everybody,
I sometimes see the following error logged by a twisted application, it
only happens sporadically and I cannot even reproduce when trying to
re-execute the exact sequence of those failures. So giving an SSCCE is
quite impossible for now (sorry). Given this trace it's also hard to
On 07:57 am, techto...@gmail.com wrote:
On Mon, May 5, 2014 at 10:06 PM, wrote:
So perhaps the reason is that someone needs to do some work to
determine if
PySide is actually safe to use with the Qt reactor now and, if it is,
shuffle some code around.
I think Twisted users just need to st
On Mon, May 5, 2014 at 10:06 PM, wrote:
> On 06:49 pm, sank.dan...@gmail.com wrote:
>>>
>>> There's a 3rd party event loop for Twisted that runs on top of Qt
>>> (qt4reactor), which would
>>> allow Twisted and Qt code to run in the same thread.
>>
>> Speaking of which, why isn't that thing offici
On Tue, May 6, 2014 at 4:02 AM, Itamar Turner-Trauring
wrote:
> On 05/05/2014 03:06 PM, exar...@twistedmatrix.com wrote:
>>
>> However, I'm not even sure if the GUI reactors *should* be distributed as
>> part of the main Twisted package. They are already first-class reactors via
>> the plugin sys
On Mon, May 5, 2014 at 8:24 PM, Itamar Turner-Trauring
wrote:
> If Spyder *just* uses Qt, it's a single-threaded event loop. There's a 3rd
> party event loop for Twisted that runs on top of Qt (qt4reactor), which
> would allow Twisted and Qt code to run in the same thread.
Spyder executes interpr
Hi Laurens,
Well, Manhole looks way more advanced than my idea. I just need to
be able to tap into one way application event stream - there is no input
from the other side, so application doesn't need to prepare for that.
So, serial != terminal. There might be in future, but now I am more
interes
15 matches
Mail list logo
