-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
BUG: setitem fails on mixed-type Panel4D #8702
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
tests! |
Ah... yeah. There is a test that highlights this in my fillna bug branch, but I guess that doesn't do any good here. I'll add a test as well to this branch. |
I added in a test which captures this issue. I also added in some tests for the non-mixed-type case since it looks like there weren't any tests of setting by index at all for It looks like this only fixes setting by index for scalar values. Setting by index to a |
keep things in separate PRs it's faster/easier to review s single fix at a time |
@@ -227,3 +227,5 @@ Bug Fixes | |||
- Fixed a bug where plotting a column ``y`` and specifying a label would mutate the index name of the original DataFrame (:issue:`8494`) | |||
|
|||
- Bug in ``date_range`` where partially-specified dates would incorporate current date (:issue:`6961`) | |||
|
|||
- Bug in `_NDFrameIndexer._setitem_with_indexer` that prevented setting scalar value by indexer in mixed-type Panel4D (:issue: `8702`) |
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.
don't use internal routines the thr release notes
setitem with a mixed dtype Panel4D was failing when setting with a scalar right (something like this
Thanks. I added the issue number to |
merged via 1041dff thanks! |
Trying to set a value on a mixed-type Panel4D currently fails:
Fortunately, it looks like a simple fix. If this looks OK. I'll add a note to
v0.15.1.txt
(doesn't have a GH issue number yet).This fix is needed for my latest attempt at the fillna bug #8395.