-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Creating DataFrame Changes Time Unit of datetime64 Series #4337
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
Comments
this is not allowed in 0.12 as np.datetime64 is broken in numpy < 1.7.1 (and buggy in 0.11) what are u trying to do ? |
What do you mean by "this" when you say "this is not allowed"? I have a time series of data that has a monthly frequency. I am trying to create a DataFrame from this data. |
I mean no need to use
there is no concept of monthly in a series an index is probably what you want
|
I was going off the ideas here: http://docs.scipy.org/doc/numpy-dev/reference/arrays.datetime.html#datetime-units It does look like something is actively preventing me from using any timeunit other than ns:
|
Use pandas features see here: datetimes are stored as you should be thinking about using lots of goodies and neat ways to represent data |
I would argue that even using those feature, there is still some oddities here:
Theoretically the freq of the date range can be inferred from the datetime units provided. |
In other words, I should not have to say:
|
explicity using |
I suppose you example above, passing a |
created #4341 to track the issue. |
I think you mean #4341 |
I stand corrected |
@jreback I wasn't trying to be a jerk, I just wanted to refer any future visitors (my self included) to the thread to the updated issue. |
On pandas v0.11.0, For example:
but then:
The text was updated successfully, but these errors were encountered: