Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strategy for nanosecond datetime #149

Open
lmazuel opened this issue Feb 28, 2019 · 0 comments
Open

Strategy for nanosecond datetime #149

lmazuel opened this issue Feb 28, 2019 · 0 comments

Comments

@lmazuel
Copy link
Member

lmazuel commented Feb 28, 2019

We cannot model it in Python and the datetime native object (and we won't use numpy just for that with datetime64).
Problem is mostly on deserialization, that will truncate the last numbers. On serialization, msrest accepts datetime or string, so customers can be responsible to provide a string instead of a datetime and we will send it.

I was thinking that maybe on deserialization, if we detect nanoseconds usage, we might disable parsing and return a string instead. That would allow roundtrip scenario, and in some scenarios when we don't even care about this date (update password, etc.), that should be enough.
However, for people who cares, this would be a breaking change.

To be thought....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant