Tom,
I guess LineReceiver can help you with that, it's a matter of using a
different delimiter. Here is a rough sketch of something you can start
exploring:
from __future__ import print_function
from twisted.internet import reactor, protocol, endpoints, defer
from twisted.protocols import basic
On 2017-02-26, at 23:51, Jean-Paul Calderone wrote:
> I'm looking at some recent trunk commits (also, others) that seem to have
> non-trivial untested code at at ReviewProcess. I can't tell if the codecov
> reports are wrong or if the development process
On 2016-12-29, at 12:23, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote:
>
>> On Dec 27, 2016, at 19:15, ex vito <ex.vitor...@gmail.com> wrote:
>>
>> Other than looking for confirmation, I have a fix which I included two
>> isolated com
On 2016-12-23, at 4:33, Amber Hawkie Brown wrote:
> [...]
>
> You can get the tarball and the NEWS file at
> https://twistedmatrix.com/Releases/rc/16.7.0rc1/ , or you can try it out from
> PyPI:
>
> python -m pip install Twisted==16.7.0rc1
>
> Please test it,
Dear all,
While working on http://twistedmatrix.com/trac/ticket/8912 and the associated
PR at https://github.com/twisted/twisted/pull/647 I hit a segmentation fault on
a test I was preparing.
I think narrowed it down Linux + Python 2, but I'm not 100% sure. Can anyone
please confirm the code
On 2016-12-17, at 23:18, Glyph Lefkowitz wrote:
> On Dec 17, 2016, at 6:11 AM, exvito here wrote:
[...]
>> Thanks for your input Cory and Glyph.
>>
>> I do agree that a well written protocol should not
>> self.transport.write after
On 2016-12-23, at 21:22, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote:
>> On Dec 23, 2016, at 12:31 PM, Glyph Lefkowitz <gl...@twistedmatrix.com>
>> wrote:
>>
>>> On Dec 23, 2016, at 3:49 AM, ex vito <ex.vitor...@gmail.com> wrote:
>>>
To the Twisted infrastructure maintainers,
First and foremost, thanks for your continued efforts and keeping things
running.
Second, the certificate I'm getting for https://speed.twistedmatrix.com is
issued to a common name "twistedmatrix.com" with no subject alternative names
matching
On 2017-09-18, at 16:35, Moshe Zadka <zadka.mo...@gmail.com> wrote:
> On Mon, Sep 11, 2017 at 2:44 AM ex vito <ex.vitor...@gmail.com> wrote:
> Sidenote: A quick, mostly backwards compatible, change could probably add cwd
> to the existing per-process tuple in self.proce
On 2017-09-19, at 21:59, Goffi wrote:
> I'm using Sqlite3 module through Twisted's enterpirse.adbapi, I create the
> ConnectionPool instance like this:
>
> self.dbpool = ConnectionPool("sqlite3", db_filename,
> check_same_thread=False)
>
> You can see the code at
>
On 2017-09-19, at 15:49, Moshe Zadka <zadka.mo...@gmail.com> wrote:
> On Tue, Sep 19, 2017 at 3:51 AM ex vito <ex.vitor...@gmail.com> wrote:
>
> Other than that, again, per that section's rules, not being a commiter
> myself, I'm in no position to approve such a change
On 2017-09-21, at 2:13, Moshe Zadka wrote:
> OK I opened a ticket with a plan, after discussing with Mark Williams.
>
> 1. Make a custom class that implements the Sequence ABC and pretends to be
> sized the old size.
> 2. Internally all access will be moved to attributes
> The options I see:
>
> 1. Move processes to a private attribute, deprecate processors, then do it.
From an abstraction standpoint, that makes sense. Probably the same could be
said about the other process related dict attributes like protocols, delay,
etc., though. They all seem to be "name"
On 2017-11-12, at 7:32, Glyph wrote:
> I attempted to draw some attention to this with github mentions:
>
> https://github.com/twisted/treq/issues/185#issuecomment-331856235
>
> but it looks like that didn't work.
>
> Hopefully by posting it here I can motivate
On 2017-11-12, at 7:32, Glyph wrote:
> I attempted to draw some attention to this with github mentions:
>
> https://github.com/twisted/treq/issues/185#issuecomment-331856235
>
> but it looks like that didn't work.
>
> Hopefully by posting it here I can motivate
On 2017-10-25, at 21:07, Enoch W. wrote:
> Hi,
>
> I am using a self-signed CA to issue server and client(s) certificates.
>
> My server is using the standard Python ssl module.
> One client, that is using twisted.internet.ssl, consistently fails to connect
> with:
> On
On 2017-10-26, at 14:59, Enoch W. wrote:
> Thanks exvito for your detailed response.
> Re 2 & 3: You're right on the nail :-) See my previous email to Jason.
> Re 4: I can't use the high level Transport mechanism as I am using Twisted
> (most of the time) through another
17 matches
Mail list logo