-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
API/ENH: support datetime.time in a Timedelta #8698
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
cc @rockg |
Hmm... not so sure this is desirable. This would be assuming that midnight is always zero? And that times are always positive? I think it would probably be better to require users to do this conversion explicitly. side note: adding time-zones to Timedelta sounds awful! |
@shoyer hah! just putting it out there if anyone sees a need for this. I added a tests to test that this is not supported, otherwise leaving for now. |
What is the best way to convert a column of times to a timedelta? As
or
seems not very concise |
actually this is a dupe of #8343 |
as I said, I think this type is useless. Those solns's are fine for the very limited amount this comes up. An in-between soln is to allow conversion directly to |
@jreback I think it are two different things, how I understand it. In this issue, it is proposed that you can provide a |
So this as expected. Though I its pretty straightforward to add support for this directly to a Timedelta, after the notion is the same, though a
time
object can support a time-zone so not sure if this is odd (or maybe we should add an optional tz to Timedelta).The text was updated successfully, but these errors were encountered: