Re: [Twisted-Python] COMMERCIAL:Re: Is there a nice way to writetransport-agnostic protocols and servers/clients?

2017-08-17 Thread Barry Scott
On Thursday, 17 August 2017 03:03:41 BST Kevin Conway wrote: > > There is no datagram endpoints API as yet, though (see #4471), only > > stream endpoints. > > I'm not sure I understand the distinction. Endpoints supports UDP which is > a datagram based transport. From a Protocol perspective, you

Re: [Twisted-Python] COMMERCIAL:Re: Is there a nice way to writetransport-agnostic protocols and servers/clients?

2017-08-17 Thread Barry Scott
On Thursday, 17 August 2017 03:03:41 BST Kevin Conway wrote: > > There is no datagram endpoints API as yet, though (see #4471), only > > stream endpoints. > > I'm not sure I understand the distinction. Endpoints supports UDP which is > a datagram based transport. From a Protocol perspective, you

Re: [Twisted-Python] Is there a nice way to write transport-agnostic protocols and servers/clients?

2017-08-17 Thread Jean-Paul Calderone
On Thu, Aug 17, 2017 at 1:35 AM, Kevin Conway wrote: > > There is no datagram endpoints API as yet, though (see #4471), only > stream endpoints. > > I've read through the ticket. What I still don't understand is the > significance of this of this? Other than some irrelevant callbacks, what > prev

Re: [Twisted-Python] Is there a nice way to write transport-agnostic protocols and servers/clients?

2017-08-17 Thread Kevin Conway
> What UDP endpoint? There isn't one. When I say "endpoint" I'm talking about the Twisted API collection that centers around *twisted.internet.endpoints*. Is that what you're talking about? Oh... Yes, that is true. I think I was reading UNIX and saying UDP in my head. I'm really sorry for the c

Re: [Twisted-Python] Is there a nice way to write transport-agnostic protocols and servers/clients?

2017-08-17 Thread Jean-Paul Calderone
On Thu, Aug 17, 2017 at 8:52 AM, Kevin Conway wrote: > > What UDP endpoint? There isn't one. When I say "endpoint" I'm talking > about the Twisted API collection that centers around > *twisted.internet.endpoints*. Is that what you're talking about? > > Oh... Yes, that is true. I think I was re

[Twisted-Python] trial.unitest-specific segfault with lxml

2017-08-17 Thread Phil Mayers
This is an odd one; I have a simple test using the incremental xmlfile() feature of lxml, that crashes *only* if the test case inherits from trial.unittest.TestCase; it works if inheriting from unittest.TestCase. SSCCE - well, hopefully correct - here: https://gist.github.com/philmayers/387597

Re: [Twisted-Python] SSLContext not valid for TLS Server

2017-08-17 Thread Glyph
> On Aug 16, 2017, at 1:15 PM, ceeborraa wrote: > > Hi, > > I'm running Twisted 17.5.0 on Python 3.5.3 and want to create a TLS server > with Twisted. I strictly sticked to the example of echoserv_ssl.py on > http://twistedmatrix.com/documents/current/core/howto/ssl.html, but TLS > server is

Re: [Twisted-Python] trial.unitest-specific segfault with lxml

2017-08-17 Thread Tristan Seligmann
On Fri, 18 Aug 2017 at 00:47 Phil Mayers wrote: > SSCCE - well, hopefully correct - here: > > https://gist.github.com/philmayers/387597c7407ab98f159426cea5f44a69 > Note that I don't think you're allowed to catch GeneratorExit like this; normally doing so will crash your program with a RuntimeErr

Re: [Twisted-Python] trial.unitest-specific segfault with lxml

2017-08-17 Thread Phil Mayers
On 18/08/2017 07:05, Tristan Seligmann wrote: Note that I don't think you're allowed to catch GeneratorExit like this; Interesting, I cribbed that from the lxml docs. Will look into it, thanks for the pointer. Given that the crash only occurs at exit, I suspect this has something to do wit