This is wrong, don't do this.
Using utcnow() is correct, rendering the timezone should be fixed instead. If we have legacy records that used now() vs utcnow() we can either fix them in the datbase or just ignore them.
Look up django's TZ setting for details.
« Back to merge proposal
This is wrong, don't do this.
Using utcnow() is correct, rendering the timezone should be fixed instead. If we have legacy records that used now() vs utcnow() we can either fix them in the datbase or just ignore them.
Look up django's TZ setting for details.