Posted: April 2, 2010
People don’t write enough about how they catch, report, and fix bugs. I hope others will follow my lead in exposing the process more.
- Tried to read IanB’s revised webob tutorial at
- where I got annoyed by how copying and pasting the code is hard
with the “>>>” and “…” symbols. At the first example!
- Since Python-Sphinx is the issue, spent some time in #python-docs
discussing soluions with Taggnostr, including ones that other
code highlighters use.
- Thought about how IanB probably likes that the code isn’t just
cut and pastable, since it typing it in yourself is much better for learning.
Decided that I didn’t care!
- Built on Taggnostr’s jquery-based fix on the installed
- Branched and checked out Sphinx from BitBucket to work on it
it more formally…
- where I promptly made a mess of things. I don’t know jquery or
was that between my version and tip, underscore.js was added, so
using the new doctools.js file in my generated sphinx html tree
was causing some silent errors! Boy, JS seems to be hard to troubleshoot,
and not very good at failing loudly!
- After finishing my fixes, checked in the fix to BitBucked and pushed.
- Made a pull-request, where I discovered that then you pull on your own
branch at BB, it sends the request to you. This seems, hm…, unintuitive!
- After asking about it at #mercurial who answered, and #bitbucket who didn’t,
people agreed that this was, um, odd behaviour.
- So, bug time at BitBucket, where after a search, I found Bug 681…
- …which was filed by IanB!