I am plannig to upgrade twisted's buildbot in the near future. In
preperation for that, I am going to take down the production buildbot
on Tuesday, June 26, around 1600 UTC.
During that time, the result of any builds done will be lost. Thus, I'd
ask that people avoid committing to trunk during that time.
I will send a reminder before I take down the buildbot both here, and on
#twisted and #twisted-dev.
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
Hello Twisted Community,
Since I changed jobs, maintaining Twisted is no longer one of my formal professional responsibilities. There have also been a number of recent events in my personal life which have reduced the amount of free time that I have, and impending changes that will reduce it even further.
This doesn't mean that I won't be contributing to Twisted at all as part of my job (in fact I probably have something coming later this month), just that since I no longer work for an infrastructure provider, "open source qua open source" is no longer part of the job description.
As such, I've been contributing to Twisted somewhat less lately, and I expect that contribution to further decline at least for a while.
Rather than this just resulting in an overall decrease in activity, I wanted to send an explicit message asking the community for help, to try to use this as an opportunity. In the past, when prominent members of the project (myself included) have stepped back, others have stepped in to fill the void, and this has often been the catalyst for significant community growth. However, this has always been a slow, organic process, because core project members (again, myself included) haven't always been clear about when they were going to be active.
So, if you are wondering, "what can I do for Twisted"?
If you area already a commit member with repo:write, you know what to do. Get cracking.
Reply to this message. Let's get a conversation going. Maybe someone else has some good ideas.
Check out https://twisted.reviews <https://twisted.reviews/>. The one advantage of remaining on Trac (as opposed to moving fully to Github) is that you can see at a glance, by looking at which rows are not greyed out on that report, what tickets that you have the ability to submit an authoritative code review for. The rule is: external contributors can review stuff submitted by project members.
Our main hosted machine now supports Docker! Volunteer for some operational responsibilities, or move more of our infrastructure into containers so that more of the maintenance work can be reliably tested by folks without permissions to access the actual infra. Have a look over at https://github.com/twisted-infra/braid <https://github.com/twisted-infra/braid>.
Everyone's favorite owl also seems to have been somewhat more busy with non-Twisted stuff of late: volunteer to be a release manager to keep our pace of releases up!
Finish porting us to Python 3. We are very, very close: http://blog.habnab.it/twisted-depgraph/ <http://blog.habnab.it/twisted-depgraph/>
Looking forward to see what y'all can do in my (mostly) absence,
-----BEGIN PGP SIGNED MESSAGE-----
I'm very happy to release txtorcon 0.19.0. This merges most of the
development that happened over the last several months on the
release-1.x branch. Featuring:
* Full Python3 support (and universal wheels)
* Drop txsocksx and use a custom implementation (this also implements
the custom Tor SOCKS5 methods RESOLVE and RESOLVE_PTR). Uses
Automat for the state-machine.
* Drop support for older Twisted releases (12, 13 and 14 are no
* Add a top-level API object (txtorcon.Tor) that abstracts a running
Tor. Instances of this class are created with txtorcon.connect or
txtorcon.launch. These instances are intended to be "the"
high-level API and most users shouldn't need anything else.
* Integrated support for twisted.web.client.Agent, baked into
txtorcon.Tor. This allows simple, straightforward use of treq or
"raw" twisted.web.client for making client-type Web requests via
Tor. Automatically handles configuration of SOCKS ports.
* new high-level API for putting streams on specific Circuits. This
adds txtorcon.Circuit.stream_via and txtorcon.Circuit.web_agent
methods that work the same as the "Tor" equivalent methods except
they use a specific circuit. This makes
txtorcon.TorState.set_attacher the "low-level" / "expert"
interface. Most users should only need the new API.
* big revamp / re-write of the documentation, including the new
* Issue 203: https://github.com/meejah/txtorcon/issues/203
* new helper: txtorcon.Router.get_onionoo_details which downloads
JSON for a particular relay from OnionOO
* new helper: txtorcon.util.create_tbb_web_headers which returns
headers resembling a recent Tor Browser suitable for use with
Twisted or treq web agents.
* Issue 72: https://github.com/meejah/txtorcon/issues/72
* Specific SocksError subclasses for all the available SOCKS5 errors
added by https://github.com/felipedau
* (more) Python3 fixes from https://github.com/rodrigc
You can download the release from PyPI or GitHub (or of course "pip
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-----
This is a problem in twisted. Buldbot uses twisted.
To make buildbot git polling work for me, I had to make the change below.
Based on zturner comment #17 in
Win 10 Pro, Version 1703, OS Build 15063.138, 64 bit
Buildbot version: 0.9.5
Twisted version: 17.1.0
$ diff -uprN _dumbwin32proc.py.orig _dumbwin32proc.py
--- _dumbwin32proc.py.orig 2017-04-18 08:25:31.639822200 -0700
+++ _dumbwin32proc.py 2017-04-18 08:25:43.310989300 -0700
@@ -210,7 +210,7 @@ class Process(_pollingfile._PollingTimer
# TODO: error detection here. See #2787 and #4184.
self.hProcess, self.hThread, self.pid, dwTid = win32process.CreateProcess(
- command, cmdline, None, None, 1, 0, env, path, StartupInfo)
+ None, cmdline, None, None, 1, 0, env, path, StartupInfo)