Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork18.5k
BUG: Series ops with a rhs of a Timestamp raising exception (#2898)#2899
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
anybody have an issue with the API change vai |
I do. I would rather users use |
prob is I was using this with a datetime64[ns] columns |
all fixed up, restored unique behavior fyi...py3 does funny things with np.timedelta64...., its auto converts them to int when you astype('O') |
@y-p when you have a chance, can you take a look at test_timedelta in tests/test_format.py. I had to put in my own formatter to handle NaT and py3.3 change in the way printing works for timedelta64. It works and returns a string. Not sure if I need to deal with unicode in any way? thanks |
ghost commentedFeb 22, 2013
you're returning a string tha always contains pure ascii characters, |
great thanks |
@wesm any problem with merging this in? |
unique of a Series now returns a Series _index.convert_scalar now will ignore a ndarray object if the lhs is timelike (eg a non-scalar that is a series/ndarray is passed)BUG: py3 issue with np.datetime64 conversion added array_timedelta_to_int conversions in tslib.pyx removed unique changesDOC: added docs to timeseries for timedeltas and v0.11.0 whatsnew minor fixing of doc refernce in v0.10.0 updated RELASE.rstENH: added ability for Series to set its dtype if it detects all timedelta like objectsENH: added null checking and NaT support for timedelta64 added formatter for timedelta64 added setting via np.nan for NaT values (similar to datetime64[ns] support)FMT: fixed timedelta64[ns] formatting (was breaking on py3.3) had to roll a new printer (repr_timedelta64) rather than use default str(x)ENH: increased robustness in detection/conversion of timedelta64 that are intermixed with np.nan,NaT,iNaT
BUG: Series ops with a rhs of a Timestamp raising exception (#2898)
ghost commentedMar 18, 2013
Putting example from docs here, for readers of RELEASE.txt
|
to convert to a scalar (but didn't need conversion)
timedelta64[ns]
dtype (if all passed objects are timedelta like)