-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
ENH/CLN: support enhanced timedelta64 operations/conversions #4822
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
Conversation
@@ -1719,6 +1736,8 @@ def convert(self, values, nan_rep, encoding): | |||
else: | |||
self.data = np.asarray(self.data, dtype='M8[ns]') | |||
|
|||
elif dtype == u('timedelta64'): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it matter to compare to unicode? (I honestly don't know...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually it does because the data is stored as bytes (and reconverted) in read back by pytables (I think)
these are comparing vs stored data
@cpcloud this ended up morphing...but now have |
…query and append (GH3577)
…rom a series of functions in core/common)
API: add full timedelta parsing and conversion to np.timedelta64[ns]
All of the experimentalists using pandas will now be chomping at the bit for One does not simply .... implement 😄 |
hah...I just returned a Series, easier (and pretty close actually) |
|
ENH/CLN: support enhanced timedelta64 operations/conversions
closes .#3577
realted #3009
to_timedelta
to convert string/integer to timedeltas