Runestone Issue: Python unittest feedback table column headers Expected & Actual in wrong order

In Python unit tests, the column headers of Actual and Expected are in the wrong order. It doesn't matter if you use assertEqual, but if you use assertIn or assertNotEqual then the first argument is what is expected. Kate (@kmcdonnell2) and I confirmed that they are in the right order in Java books, but not in Python books.
Python feedback for

  self.assertIn("%", self.getEditorText().replace(" ", ""), "Use % with newTime and 12.")
  self.assertEqual(clockTime, 4, "Testing that clockTime has the correct value." )
  self.assertNotIn("4",self.getEditorText(),"Testing that you didn't hardcode the answer. Make sure to calculate it!")

generates the following where the first column should be Expected Value, not Actual, which makes a difference for the 1st and 3rd rows.

Compared to Java books where Expected and Actual are in the correct order:

No source file or test path is named. Start by locating the Python unittest feedback-table generation using the reported assertIn, assertEqual, and assertNotIn examples, then compare its column order with the Java feedback shown in the issue; done means Expected Value appears before Actual Value and the affected rows display the correct values.