May not be a bug depending on your perspective.
In the marathon RAML spec it says it uses `datetime`.
But the call chain:
public String toString()
Outputs this date-time as a String, such as 2007-12-03T10:15:30+01:00.
The output will be one of the following ISO-8601 formats:
The format used will be the shortest that outputs the full value of the time where the omitted parts are implied to be zero.
This can cause bugs when the timestamps are "perfect" because they lack the milliseconds that they have 999/1000 times.
Specifically in the python library Yelp uses, the timestamp format is assumed here:
So it is arguably a bug in that library. Can you confirm: should we expect milliseconds in the timestamp outputs for datetime from Marathon?