hi there, folks:
I'd really like to release 0.7.0 but I would like it to be at least a
little bit tested before I do so. Could those of you with CVS trees check
everything out and see if it performs as advertised? Deeper bugs than
that will have to wait for the next release, but I'd at least like to know
if it works for someone other than me.
______ __ __ _____ _ _
| ____ | \_/ |_____] |_____|
|_____| |_____ | | | |
@ t w i s t e d m a t r i x . c o m
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
- 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
Please see the NEWS.rst file and download the tarball at
https://twistedmatrix.com/Releases/rc/17.5.0rc2/ . (rc1 fell to metadata
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.
Amber Brown (HawkOwl)
As we're splitting the project into more parts, we may have to do Github org surgery to move projects around.
In particular, recently, twisted.python.url got split out into a new package called 'hyperlink', which we were initially thinking the Twisted org would adopt. (As it happens a different org will probably adopt it, more on that later.) Adi created a repo to allow Mahmoud to do this, and gave him permissions on said repo.
I just deleted this repo :-). In the future, the right way to do this is to have the owner transfer the repo over to the relevant org (this is in the "danger zone" in the github UI). Creating empty repos to move projects around breaks a whole bunch of github functionality (clones of the original repo can't update, ticket & PR history doesn't transfer over and can't be moved, links to forks get broken) and we should generally not do it.
-----BEGIN PGP SIGNED MESSAGE-----
Fixing another regression, 0.19.3 causes txtorcon to (once again)
correctly work with SocksPort lines containing unix socket options
when used with txtorcon.connect(). Thas bug was introduced in 0.19.0
which reduced the number of GETINFO and GETCONF calls (to help
You can download the release from PyPI or GitHub (or of
course "pip install txtorcon"):
Releases are also available from the hidden service:
You can verify the sha256sum of both by running the following 4 lines
in a shell wherever you have the files downloaded:
cat <<EOF | sha256sum --check
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
I'm a beginner with Twisted, and I would like to get involved. I spoke to a
few people at the Pycon 2017 Sprints and was hoping to learn how to start
my contribution by working on the documentation and testing. Please let me
know how I can get involved.
In going through the instructions on
I noticed an error in the invocation of the twistedchecker-trunk-diff
The change needed is:
# On Linux/OSX there is a helper to only raise error for the diff
I am happy to make the change, but I don't currently have edit
permissions to the wiki (for reference, my trac username is