Managing multiple geographies and time zones in Django - part 2 Last month, I demonstrated how to handle geographies in a Django app, so that: users can only interact with objects attached to their geography; users see datetimes in the local time zone of their geography. This is an example of multi-tenancy: each geography is a tenant. Then I had an uncommon requirement: let a user account interact with several geographies. It’s interesting because it doesn’t fit into the data model at all...
