Repository: Scille/umongo (python)

Issue:
ValueError: microsecond must be in 0..999999
Hello, all

I've got a new error after the v2.0.0 milestone, likely relating to #172. Here's the error text:

```python
  File "/Users/space/Documents/Programming/dt-blog-platform/api-server/db/objs.py", line 268, in commit
    self.updatedon = datetime.datetime.utcnow()
  File "/var/root/.local/share/virtualenvs/api-server-DI-zCP9m/lib/python3.6/site-packages/umongo/document.py", line 295, in __setattr__
    self._data.set(name, value, to_raise=AttributeError)
  File "/var/root/.local/share/virtualenvs/api-server-DI-zCP9m/lib/python3.6/site-packages/umongo/data_proxy.py", line 152, in set
    value = field._deserialize(value, name, None)
  File "/var/root/.local/share/virtualenvs/api-server-DI-zCP9m/lib/python3.6/site-packages/umongo/fields.py", line 245, in _deserialize
    return ret.replace(microsecond=round(ret.microsecond, -3))
ValueError: microsecond must be in 0..999999
```

My guess is something funky is going on either with my system, or maybe the round isn't working properly? Not too sure, but this should be a simple one.

The way I did this is set a `StrictDateTimeField` equal to `datetime.datetime.utcnow()` in an overriden `commit` method. Ex:

```python
@instance.register
class Foo(Document):
    name = fields.StringField()
    updatedon = fields.StrictDateTimeField()

    def commit(self, *args, **kwargs):
        self.updatedon = datetime.datetime.utcnow()
        return super(Foo, self).commit(*args, **kwargs)
```

This error happens when calling the commit method on the object.

Thanks in advance!

Pull request description:
Fix millisecond overflow issue in StrictDateTimeField
Actually fixes #189...

Patch:
diff --git a/umongo/fields.py b/umongo/fields.py
index 2cb87e3..c2ba09a 100644
--- a/umongo/fields.py
+++ b/umongo/fields.py
@@ -248,9 +248,7 @@ class StrictDateTimeField(BaseField, ma_bonus_fields.StrictDateTime):
             ret = self._set_tz_awareness(value)
         else:
             ret = super()._deserialize(value, attr, data)
-        # MongoDB stores datetimes with a millisecond precision.
-        # Don't keep more precision in the object than in the database.
-        return ret.replace(microsecond=round(ret.microsecond, -3))
+        return _round_to_millisecond(ret)
 
     def _deserialize_from_mongo(self, value):
         return self._set_tz_awareness(value)


Test patch:
diff --git a/tests/test_fields.py b/tests/test_fields.py
index d4d2133..9b90b05 100644
--- a/tests/test_fields.py
+++ b/tests/test_fields.py
@@ -243,6 +243,11 @@ class TestFields(BaseTest):
         s = MySchema()
         data, _ = s.load({'a': dt.datetime(2016, 8, 6, 12, 30, 30, 123456)})
         assert data['a'].microsecond == 123000
+        data, _ = s.load({'a': dt.datetime(2016, 8, 6, 12, 59, 59, 999876)})
+        assert data['a'].hour == 13
+        assert data['a'].minute == 0
+        assert data['a'].second == 0
+        assert data['a'].microsecond == 0
 
     def test_date(self):