These sorts of `assertEquals()` between two timestamps can cause confusing errors, I'm getting:

```python
datetime.datetime(2013, 6, 26, 20, 35, 0, 966609, tzinfo=<UTC>) != datetime.datetime(2013, 7, 14, 20, 35, 0, 969450, tzinfo=<UTC>)
```

This is because a few milliseconds can pass between `timezone.now()` and when the row is actually written in the db. Again I'd question the use of this test because if this sort of writing of normal Django fields to a database fails then we've got bigger problems. It's safe to assume that Django will behave.