Skip to main content

Python Contributor!

I'm rather proud to report that my first contribution to the Python code base has been committed in changeset 80421. To aid in my nostalgia I'm going to discuss what I did and why.

It started a long time ago, I think this post by Jesse Noller inspired me. A new mailing list was set up to encourage more core development, the aim was to get new contributors to the Python codebase. At the same time the Python developers guide was  heavily edited and was made available at

The call was put out for simple contributions - documentation, examples, improving testing coverage for the standard library and relatively easy beginner tasks to become familiar with the development process.

Using a coverage tool written by Ned Batchelder I generated a list of test coverage for each standard library module. After looking down the list of modules with low test coverage I decided to tackle functools. This was a good trade off in terms of its test coverage was really low (~30%), and personal interest as its a module that I regularly use.
The functools module is for higher-order functions: functions that act on or return other functions. In general, any callable object can be treated as a function for the purposes of this module.
After a look though the source code it appeared the coverage is so low because a function that is implemented in Python get unconditionally replaced with a C equivalent (if present). There were others functions implemented in C that could have been written in pure Python as well.

Modifying the functools module slightly and creating a few more tests was relatively straight forward. I created an issue on Python's bug tracker: and uploaded my patch.

I emailed the core mentorship mailing list to get advice with one design decision and received awesome replies from some core developers that I highly respect; Nick Coghlan, Raymond Hettinger, Antoine Pitrou, √Čric Araujo and Ezio Melotti all went out of their way to help. There was a little bit of debate over the changes and the review cycle went around five times over the course of a year.

I must admit I was surprised by how long it would take for feedback after I uploaded a new revision of the patch. At my work code reviews are rather highly prioritized, although I understand the nature of open source means people will contribute their time where and when they want. Code coverage patches don't really feature highly on most peoples interests, although I think it helped that I had emailed the core mentorship group - at least some people were aware it would be my first contribution.

That said I use Python so much and really wanted to get involved. My itch wasn't a particular issue - I wasn't passionate about the test coverage but rather I just wanted to give something back. Sure I've been using and promoting javascript more and more recently but Python will always be my language in a time of need.


Popular posts from this blog

Matplotlib in Django

The official django tutorial is very good, it stops short of displaying
data with matplotlib - which could be very handy for dsp or automated
testing. This is an extension to the tutorial. So first you must do the
official tutorial!
Complete the tutorial (as of writing this up to part 4).

Adding an image to a view

To start with we will take a static image from the hard drive and
display it on the polls index page.
Usually if it really is a static image this would be managed by the
webserver eg apache. For introduction purposes we will get django to
serve the static image. To do this we first need to change the

Change the template
At the moment poll_list.html probably looks something like this:

<h1>Django test app - Polls</h1> {% if object_list %} <ul> {% for object in object_list %} <li><a href="/polls/{{}}">{{ object.question }}</a></li> {% endfor %} </ul> {% else %} <p>No polls are available.</p> …

Homomorphic encryption using RSA

I recently had cause to briefly look into Homomorphic Encryption, the process of carrying out computations on encrypted data. This technique allows for privacy preserving computation. Fully homomorphic encryption (FHE) allows both addition and multiplication, but is (currently) impractically slow.

Partially homomorphic encryption just has to meet one of these criteria and can be much more efficient.
An unintended, but well-known, malleability in the common RSA algorithm means that the multiplication of ciphertexts is equal to the multiplication of the original messages. So unpadded RSA is a partially homomorphic encryption system.

RSA is beautiful in how simple it is. See wikipedia to see how to generate the public (e, m) and private keys (d, m).

Given a message x it is encrypted with the public keys it to get the ciphertext C(x)with:

To decrypt a ciphertext

Bluetooth with Python 3.3

Since about version 3.3 Python supports Bluetooth sockets natively. To put this to the test I got hold of an iRacer from sparkfun. To send to New Zealand the cost was $60. The toy has an on-board Bluetooth radio that supports the RFCOMM transport protocol.

The drive protocol is dead easy, you send single byte instructions when a direction or speed change is required. The bytes are broken into two nibbles: 0xXY where X is the direction and Y is the speed. For example the byte 0x16 means forwards at mid-speed. I was surprised to note the car continues carrying out the last given demand!

I let pairing get dealt with by the operating system. The code to create a Car object that is drivable over Bluetooth is very straight forward in pure Python: