L. Daniel Burr and I got up to some interesting reflections on Twisted's
logging system in this Ampoule PR:
https://github.com/twisted/ampoule/pull/29/files/268e4dcd8072d37780fd7ff0d875e614aa7da040#r299336179
Klein and Crossbar.io seem relevant as well
https://crossbario.com/blog/Going-Asynchronous-from-Flask-to-Twisted-Klein/
On Thu, Jul 11, 2019 at 1:46 AM Scott, Barry
wrote:
> On Tuesday, 9 July 2019 22:04:11 BST Tom Most wrote:
>
> ...snip...
>
> > The reactor's own thread pool is really for
On Thursday, 11 July 2019 11:00:33 BST Jarosław Fedewicz wrote:
> So far, I tried to minimize a test case, but it seems like it's really
> picky about what environment it's running in. One of those cases where "it
> works on my machine", I suppose. The versions are as follows:
>
>
On Thursday, 11 July 2019 12:00:33 CEST Jarosław Fedewicz wrote:
> Is there a neat way to list all pyOpenSSL objects in a running Twisted
> program? Or maybe TCPConnection objects, since those might hook to
> the zope.interface machinery?
Not specific to Twisted, but you can get a list of all
So far, I tried to minimize a test case, but it seems like it's really
picky about what environment it's running in. One of those cases where "it
works on my machine", I suppose. The versions are as follows:
cryptography==2.7
pyOpenSSL==19.0.0
asn1crypto==0.24.0
pyasn1==0.4.5
On dt., jul. 09 2019, Thomas Westfeld wrote:
Dear all,
I would love to see a new release of ldaptor, which incorporates
the recent compatibility fixes with python 3.
Furthermore I have submitted a new pull request for ticket #9596
and revised my pull request about documentation fixes
On Tuesday, 9 July 2019 22:04:11 BST Tom Most wrote:
...snip...
> The reactor's own thread pool is really for DNS
> resolution.
Is that still true in the default case? We are use the twisted code that talks
to DNS servers as the threaded resolver adds too much latency.
> You risk deadlocks in
Hi Jarosław!
> On Jul 1, 2019, at 4:48 PM, Jarosław Fedewicz
> wrote:
>
> I have written a simple service which takes data from network, massages it
> until it's useful enough, and sends the results out periodically via HTTP to
> an API.
A reasonable start :-).
> It all works for a while,
