I just tidied up this bug. It started off as a Django1.7 bug, then it got retitled to a Python3 bug.
Then I wondered if maybe I should have cloned it, and retitled the original back to the original value, and closed it. If you want to refine my efforts, feel free to do so.
Thanks
---------- Forwarded message ---------- From: Debian Bug Tracking System<owner@bugs.debian.org> Date: 9 September 2014 16:06 Subject: Processed: not a django1.7 bug To: Brian May <brian@microcomaustralia.com.au>