- when answer not correct, show both the given and correct string in separate
markup. we use red/green for the given string to indicate what was correct,
but we use grey rather than red on the correct string to indicate what was
missing, as red is misleading
- colours can now be customized in css with .typeGood, .typeBad and
.typeMissing
- answer now shown in monospace so given/correct lines up; can be customized
with code#typeans
- do away with 'correct answer was' text that people didn't like
Python used to use C-style division, where division of two ints was
truncated, and division involving a float resulted in a float.
This is confusing, because you often can't tell from looking at a
line of code in isolation what sort of division it's supposed to do.
With 'from __future__ import division' Python ensures that division is
always explicit.
// means (floored) integer division
/ means float division
regardless of argument types.
This should make the source a bit clearer now, as well as removing one
obstacle if Anki is ever ported to Python 3.
