On May 25, 2017, at 11:35 PM, Amber Brown wrote:

Hi everyone,

Fresh from PyCon US, comes a 17.5 prerelease. Fancy things in this release:

- twisted.python.url has been spun out into the new 'hyperlink' package; importing twisted.python.url is now a compatibility alias - Support for OpenSSL 1.1.0. - Fixes around the reactor DNS resolver changes in 17.1, solving all known regressions - Deferred.asFuture and Deferred.fromFuture, to allow you to map asyncio Futures to Twisted Deferreds and vice versa, for use the with Python 3+ asyncioreactor in Twisted - Support for TLS 1.3 ciphersuites, in advance of a released OpenSSL to enable the protocol - Further Python 3 support in twisted.web, initial support in twisted.mail.smtp

Please see the NEWS.rst file and download the tarball at https://twistedmatrix.com/Releases/rc/17.5.0rc2/ https://twistedmatrix.com/Releases/rc/17.5.0rc2/ . (rc1 fell to metadata mishaps!)

Let me know if you notice anything out of the ordinary. If there's no problems, it'll release in the next week or so.

Happily, although lots of work happened at the sprints this year, little of it was landed hastily; the things that did land quickly were fixes for long-standing regressions. So it is my hope that this will be a bit more stable than has been characteristic of our post-PyCon releases :-). The possibility for a 17.1.1 does remain open depending on how this release works out for those affected by previous regressions. Please test! -glyph

Hi Amber, I have tested Twisted 17.5.0rc2 with latest Scrapy: - the issue we have with our resolver in Python 2 looks fixed indeed, thank you for this (https://twistedmatrix.com/trac/ticket/9137)

- Support for OpenSSL 1.1.0.

- I tested with OpenSSL 1.1 and am still seeing what I reported on the mailing list, about elliptic curves: https://twistedmatrix.com/pipermail/twisted-web/2017-April/005293.html is there a chance of getting it fixed too in 17.5? - I also commented on GitHub about issues with ESMTPSenderFactory and Python 3 with a couple of fixes I tried locally in twisted/mail/smtp.py (but I did not open a ticket on Trac unfortunately so it may have been unnoticed) https://github.com/scrapy/scrapy/issues/2375#issuecomment-299226510 Thanks. /Paul On Fri, May 26, 2017 at 8:35 AM, Amber Brown wrote:

Hi everyone,

Fresh from PyCon US, comes a 17.5 prerelease. Fancy things in this release:

- twisted.python.url has been spun out into the new 'hyperlink' package; importing twisted.python.url is now a compatibility alias - Support for OpenSSL 1.1.0. - Fixes around the reactor DNS resolver changes in 17.1, solving all known regressions - Deferred.asFuture and Deferred.fromFuture, to allow you to map asyncio Futures to Twisted Deferreds and vice versa, for use the with Python 3+ asyncioreactor in Twisted - Support for TLS 1.3 ciphersuites, in advance of a released OpenSSL to enable the protocol - Further Python 3 support in twisted.web, initial support in twisted.mail.smtp

Please see the NEWS.rst file and download the tarball at https://twistedmatrix.com/Releases/rc/17.5.0rc2/ . (rc1 fell to metadata mishaps!)

Let me know if you notice anything out of the ordinary. If there's no problems, it'll release in the next week or so.

Twisted Regards,

Amber Brown (HawkOwl)

_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

On May 26, 2017, at 4:38 AM, Jean-Paul Calderone wrote:

Some of the txkube problems have been resolved but either not entirely or some new ones have been introduced. Attached is a log of the failures from the unit test suite. I haven't investigated these new errors in depth yet so I won't say whether these are txkube's fault or Twisted's fault... but at least something is at fault.

I do think we need to block the final release until we at least know where the responsibility lies for these tracebacks :-\. These all still pass on 16.6.0 I presume?

On 30 May 2017, at 05:27, Glyph wrote:

...

On May 26, 2017, at 4:38 AM, Jean-Paul Calderone mailto:exarkun@twistedmatrix.com> wrote:

Some of the txkube problems have been resolved but either not entirely or some new ones have been introduced. Attached is a log of the failures from the unit test suite. I haven't investigated these new errors in depth yet so I won't say whether these are txkube's fault or Twisted's fault... but at least something is at fault.

I do think we need to block the final release until we at least know where the responsibility lies for these tracebacks :-\. These all still pass on 16.6.0 I presume?

I investigated them, they're all due to Agent changes -- how they don't use connectSSL anymore, and instead use a wrapped TCP port, and how Agent now uses HostnameEndpoint's GAI resolving. I put up some fixes (although not up to spec for merge) here for JP: https://github.com/LeastAuthority/txkube/pull/135 https://github.com/LeastAuthority/txkube/pull/135 I would put these down to an issue in txkube, even if it's not txkube's fault, it's just that Twisted does things differently (and in the case of not using connectSSL, imo better :) ). - Amber