Note: a future improvement would be to start using timezone-aware datetime objects, but this will cause problems with existing cache data (can't compare timezone-aware and timezone-naive datetimes). It would be best to do this at the same time as a release that includes changes to request matching logic (i.e., new cache keys).
Fixes #237; related to #195
Note: a future improvement would be to start using timezone-aware datetime objects, but this will cause problems with existing cache data (can't compare timezone-aware and timezone-naive datetimes). It would be best to do this at the same time as a release that includes changes to request matching logic (i.e., new cache keys).