-
-
Notifications
You must be signed in to change notification settings - Fork 18.3k
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
Adding Period and Offset not implemented #6779
Comments
You want this, but also ability to do it with an offset. What if the offset is incompatible to the inferred_freq, raise?
|
Hmm, maybe that is sufficient. I guess I was expecting to work in both cases with a conformable offset, so I can treat period and timestamp the same and not special case everything. I'm starting to think this is a design problem on our end though and we should special case for PeriodIndex vs DatetimeIndex with a freq. I'm not really sure. I'd like to be able to treat them both the same, but I don't know if that's a reasonable expectation. |
hmm. they should have the same API, but right now they inherit from the base class separately, so this is kind of tricky This will fix it (and its not really that hard), just need to find time for this: #6469 But I agree they should be pretty comparable. That said, I think we can leave this issue open for now (i'll link to the other one), for reference |
This seems to work now:
and was closed by #7966 (which already included tests for this) |
This works
This doesn't. Shouldn't it? Workaround is to convert with
to_timestamp
.The text was updated successfully, but these errors were encountered: