Skip to main content

Getting set up with Twisted development

·2 mins

I haven’t contributed much to Twisted recently, but today I’d really like to get my new Deferred documentation ready for review.

To my knowledge, the only sensible way to actually work on Twisted code is using Combinator. With it, I can make branches, commit to those branches, merge in updates from trunk and when my branch is approved, actually land it. All of this is described more fully in Twisted’s pioneering Ultimate Quality Development System.

Combinator works by convention, so its source must live within a Divmod/trunk directory. Since I have the code in a colocated Bazaar branch in ~/src/, I created a new directory under ~/src/ called Divmod and symlinked trunk to it, approximating the instructions on the Combinator page.

$ cd src
$ mkdir Divmod
$ cd Divmod
$ ln -s ~/src/ trunk

Trying to actually use Combinator only got me stack traces and warnings though, so I poked around in the source code and now have a shell script in ~/src/ that does this:

export COMBINATOR_PROJECTS=/home/jml/src
eval `python ~/src/Divmod/trunk/Combinator/`

Sourcing that script works:

  $ .  ~/src/

After that, I blew away my checkout of Twisted and made a newer, Combinator-friendly one:

$ rm -rf ~/src/Twisted
$ chbranch Twisted trunk \

All a little bit of a hassle, but worth it to get back into the swing of contributing to Twisted.