Minor comment change.

diff --git a/enhance_table.py b/enhance_table.py
index 975abd87264f14b8acb89f4d2cc99b8e5b95a5f7..c5c11c22bfe1d52518243e13a279ad800c77301d 100755 (executable)
--- a/enhance_table.py
+++ b/enhance_table.py
@@ -95,13 +95,13 @@ for line in lines[1:]:
         db[district][date] = {'new_infections': int(district_data)}
 sorted_dates.sort()
 
         db[district][date] = {'new_infections': int(district_data)}
 sorted_dates.sort()
 

-# Define and move sum_district from end to start.
+# In LaGeSo's data, the last "district" is actually the sum of all districts /
+# the whole of Berlin.  For our district order, move it in front of the other
+# districts, as its numbers are the most interesting, so in the table views
+# we want to see it first.

 sum_district = sorted_districts.pop()
 sorted_districts.insert(0, sum_district)
 
 sum_district = sorted_districts.pop()
 sorted_districts.insert(0, sum_district)
 

-# In LaGeSo's data, the last "district" is actually the sum of all districts /
-# the whole of Berlin.
-#

 # Fail on any day where the "sum" district's new infections are not the proper
 # sum of the individual districts new infections.  Yes, sometimes Lageso sends
 # data that is troubled in this way.  It will then have to be fixed manually in
 # Fail on any day where the "sum" district's new infections are not the proper
 # sum of the individual districts new infections.  Yes, sometimes Lageso sends
 # data that is troubled in this way.  It will then have to be fixed manually in