Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
BUG: nested dict construction timedelta #11129
Comments
|
Are you sure you meant to reference #11115 (Interpolate erroneously fills NaNs at beginning of sequence when limit_direction == 'both') on this issue? |
|
Sorry, wrong issue. Edited above, thanks! |
|
@chris-b1 yep this prob need just a change to |
jreback
added this to the
Next Major Release
milestone
Sep 16, 2015
jreback
added Difficulty Novice Effort Low
labels
Sep 16, 2015
|
FYI, this actually works for |
|
what exactly is not matching for the hash of a |
|
right now the
I tried changing the hash definition as below, patterned after
|
|
hmm, try that. (hash change looks ok). But I think we also need the change to |
chris-b1
referenced
this issue
Sep 17, 2015
Merged
BUG: nested construction with timedelta #11129 #11134
jreback
modified the milestone: 0.17.0, Next Major Release
Sep 17, 2015
|
We should definitely match the timedelta hash on our subclass. I would consider that also a bug. |
chris-b1
added a commit
to chris-b1/pandas
that referenced
this issue
Sep 17, 2015
|
|
chris-b1 |
961dd47
|
jreback
closed this
in #11134
Sep 17, 2015
jreback
added a commit
that referenced
this issue
Sep 17, 2015
|
|
jreback |
6785475
|
yarikoptic
added a commit
to neurodebian/pandas
that referenced
this issue
Oct 11, 2015
|
|
yarikoptic |
cdbb0ff
|
chris-b1 commentedSep 16, 2015
Related to #10160 / PR pydata#10269
This seems to happen because
Timedeltadoesn't have hash equality withdatetime.timedeltaIt could easily be worked around here, but I was wondering if there's any reason not to makeTimedeltawork likeTimestampand match hashes if above a certain resolution?