Skip to content

Backport PR #45287 on branch 1.4.x (BUG: frame[x].loc[y] inconsistent with frame.at[x, y]) (#45287) #47921

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

Merged
merged 4 commits into from
Aug 3, 2022

Conversation

phofl
Copy link
Member

@phofl phofl commented Aug 1, 2022

Backport PR #45287, see #47867 (comment)

Lets see if this works

@phofl phofl changed the title Backport PR #45287 on branch 1.4.x (BUG: frame[x].loc[y] inconsistent with frame.at[x, y]) (#45287 ) Patrick Hoefler* 20.07.22, 15:36 Backport PR #45287 on branch 1.4.x (BUG: frame[x].loc[y] inconsistent with frame.at[x, y]) (#45287) Aug 1, 2022
@simonjayhawkins simonjayhawkins added Indexing Related to indexing on series/frames, not to indexes themselves Regression Functionality that used to work in a prior pandas version labels Aug 2, 2022
@simonjayhawkins simonjayhawkins added this to the 1.4.4 milestone Aug 2, 2022
@simonjayhawkins
Copy link
Member

don't worry about the mypy failures. imo it is main that is wrong since we have traditionally always run the typing validation against the latest numpy release, which is what's happening here.

@phofl
Copy link
Member Author

phofl commented Aug 3, 2022

Yep thx

@simonjayhawkins
Copy link
Member

Lets see if this works

Thanks @phofl merge when ready.

@@ -16,6 +16,7 @@ Fixed regressions
~~~~~~~~~~~~~~~~~
- Fixed regression in :func:`concat` materializing :class:`Index` during sorting even if :class:`Index` was already sorted (:issue:`47501`)
- Fixed regression in setting ``None`` or non-string value into a ``string``-dtype Series using a mask (:issue:`47628`)
- Fixed regression in :meth:`loc.__getitem__` with a list of keys causing an internal inconsistency that could lead to a disconnect between ``frame.at[x, y]`` vs ``frame[y].loc[x]`` (:issue:`22372`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would probably move this to bug fix and put reference to the new issue in the regression section

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also add a release note for the #47867 issue in the regression section (in the addition to the bugfix release note)

or are you doing this when you add the test?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wanted to do this with the test, but no strong preference

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure. merge when ready.

@phofl
Copy link
Member Author

phofl commented Aug 3, 2022

Failure unrelated, see #47945

@phofl phofl merged commit 015f67d into pandas-dev:1.4.x Aug 3, 2022
@phofl phofl deleted the backport_indexing_regression branch August 3, 2022 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Indexing Related to indexing on series/frames, not to indexes themselves Regression Functionality that used to work in a prior pandas version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants