Malformed Last Updated field about eve HOT 7 CLOSED

I've teste with Eve==2.0.2 too, same problem

from eve.

This is intended behavior, see this for the reasoning around it.

from eve.

Ok, but Eve set UTC time here, does not make sense to remove tzinfo

from eve.

Hmm, that's the oplog push code, and in a conditional branch only executed when the last update info not available. Furthermore, it's set at UTC precisely because all last_updates must be timezone-less (see my link above.)

from eve.

It was only an example code, here another example.
Why _create field, that is a Date field equals to _updated on MongoDB should be timezone-less?

from eve.

A possible fix is

- updates[config.LAST_UPDATED] = datetime.utcnow().replace(microsecond=0)
+ updates[config.LAST_UPDATED] = datetime.utcnow().replace(microsecond=0, tzinfo=timezone.utc)

from eve.

Feel free to submit a PR, I'll be happy to review it.

from eve.