I just might make it.
It’s been touch and go with classes and illness and feeling overwhelmed. I’ve not had the energy to write enough analytical stuff. My backlog there is growing.
I did fix a superfun bug in my exam authoring tool. It is a classic “dynamic typing plus truthiness” bug that gets static typing folks very excited.
I have a Python object that represents true-false questions. It inherits from an abstract question object. So far, fine. It is parsable from and printable to a simple format eg:
Q: This sentence is true! + F Marks: 1 By: BJP
(Yes the sentence is true if you assume it’s true and false if you assume it’s false.)
This is fine until I used the “shuffle” option which reorganises the exam and question options. What I was getting out was:
Q: This sentence is true! + T Marks: 1 By: BJP
This is bad! And has nothing to do with shuffling. The culprit looked like this:
options = '+ T' if self.key else '+ F'
This would have worked if the key was a Boolean. But it was a string: “True” or “False”. Any non empty string is truthy so the else never gets taken.
Either types on variables or no truthiness would have flushed this out. It was damned hard to spot esp when I wrote tests that constructed the object directly and set the key to a Boolean. (Unit testing didn’t work! It needed an integration test at least.)
Two months to go…