11-27-2020, 03:42 PM
Could you give an example? Currently, internally, TACTIC always converts timestamps to naive GMT datetime objects. The reason they are naive (and assumes GMT) is because in the past we had a number of Python modules just crash when using non-naive datetime objects. We convert all timestamps to this so that all operations are with consistent datetimes. On display, it should convert to the local timezone.