Skip to content

Second vs. nanosecond resolution in encoding indexes vs datetime.datetime objects in JSON encoding #1304

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.

Sign up for GitHub

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

Jump to bottom
Closed
wesm opened this issue May 24, 2012 · 0 comments
Closed

Second vs. nanosecond resolution in encoding indexes vs datetime.datetime objects in JSON encoding #1304

wesm opened this issue May 24, 2012 · 0 comments
Labels
Bug IO Data IO issues that don't fit into a more specific label
Milestone
0.8.0

Comments

@wesm
Copy link
Member

wesm commented May 24, 2012

related to #1263

In [2]: ujson.encode(datetime.now())
Out[2]: '1337804262'

In [3]: np.array(datetime.now(), dtype='M8[ns]').view('i8')
Out[3]: array(1337804288505948000)
@wesm wesm closed this as completed in 95e1b84 May 25, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug IO Data IO issues that don't fit into a more specific label
Projects
None yet
Milestone
0.8.0
Development

No branches or pull requests
1 participant
@wesm