Time field wrong result with microseconds #464
Labels
Comments
|
Certainly looks like a bug. I'd gladly review and merge a PR fixing this. |
vuonghv
added a commit
to vuonghv/marshmallow
that referenced
this issue
Jul 16, 2016
When a Time object has microsecond value, the _serialize() method
returns the following string format: 'HH:mm:ss.SSSSSS'
marshmallow-code#464
vuonghv
added a commit
to vuonghv/marshmallow
that referenced
this issue
Jul 16, 2016
When a Time object has microsecond value, the _serialize() method
returns the following string format: 'HH:mm:ss.SSSSSS'
marshmallow-code#464
sloria
pushed a commit
that referenced
this issue
Jul 22, 2016
When a Time object has microsecond value, the _serialize() method
returns the following string format: 'HH:mm:ss.SSSSSS'
#464
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a schema with a
Timefield. When it serializes a value with microseconds, e.g.2016-05-27T11:02:35.267899, it results in2016-05-27T1.The reason are those lines:
https://github.com/marshmallow-code/marshmallow/blob/dev/marshmallow/fields.py#L911
I have no idea what your idea was behind that, @sloria .
ret[:19]would do it in my case, don't know if there might be other cases.The text was updated successfully, but these errors were encountered: