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
I have started working with Twisted and found it to be a very powerful
package. That said, some modules are not documented very thoroughly (big
surprise in the world of software, right?) and I also found some
questionable code, too.
If I were to contribute fixes/improvements, what is the submission
In this PR:
pycodestyle was disabled in trunk in order to make it easier to merge
and not have pycodestyle error out, due to the code not meeting existing
Twisted style guidelines.
So this means that the old pycodestyle is not enforced in trunk.
In this PR:
file was added to the tree. I guess in future,
if the entire tree is reformatted, then we can add that git SHA for the PR
the tree, so that that revision will be ignored during a `git blame`.
There is this pending (over 1 year) PR to add black to CI:
There are some comments in there related to documentation changes.
Can the non-documentation changes be pulled out of PR 1134 and merged to
I guess whenever black is merged to trunk, then a follow-up PR to update
`.git-blame-ignore-devs` would be required?
I'm using twisted 20.3 and python3.6.8 and Windows 10
I'm using endpoint_description with a tac file to start up a server.
But I need to disable tls 1.0 and 1.1.
I was hoping to find a parameter I could pass in to make the system only
recognise 1.2 and 1.3. But could not find anything that would do that. I
thought sslmethod would be what I wanted but that is limited to :
Must be one of: "SSLv23_METHOD", "SSLv2_METHOD", "SSLv3_METHOD",
"TLSv1_METHOD". If I choose TLSv1_METHOD, TLS1.0 and 1.1 are still enabled
and QUALYS complains and downgrades the rating to B
In the end I found _defaultMinimumTLSVersion in _sslverify.py.
I set this to TLSVersion.TLSv1_2 and that seemed to do the trick.
But I don't think I should be doing that. I think I've missed some obvious
place where I can pass in a value to change this.
Anyone know where I should be looking.
Thanks for any info
020 7223 7567
I opened https://github.com/twisted/incremental/issues/55 a few days ago, and I'm wondering if anyone has any objection to me making a fix. I'm using incremental at work on a project that uses black, so this just means I have to run black each time there is a version update -- not the end of the world, but annoying nonetheless.