Skip to content

BUG: Bug in setitem raising ValueError when setting more than one column via array #37964

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 2 commits into from
Nov 21, 2020

Conversation

phofl
Copy link
Member

@phofl phofl commented Nov 19, 2020

Did not add whatsnew, cause works on 1.1.4

Array to set has to have more or less rows than columns, otherwise bug won't occur. Wrong values would be set silently here.

This is only a regression on master, not related to any release

cc @jbrockmendel

@phofl phofl added Regression Functionality that used to work in a prior pandas version Indexing Related to indexing on series/frames, not to indexes themselves labels Nov 19, 2020
@jreback jreback added this to the 1.2 milestone Nov 20, 2020
Copy link
Contributor

@jreback jreback left a comment

Choose a reason for hiding this comment

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

lgtm. cc @jbrockmendel

@jbrockmendel
Copy link
Member

does this address the perf complaint in the OP from the linked issue?

@jbrockmendel
Copy link
Member

small comments, LGTM

@phofl
Copy link
Member Author

phofl commented Nov 21, 2020

No, only the regression raising an error.

@jbrockmendel
Copy link
Member

LGTM cc @jreback (travis failure is unrelated)

@jreback jreback merged commit e640dde into pandas-dev:master Nov 21, 2020
@jreback
Copy link
Contributor

jreback commented Nov 21, 2020

thanks @phofl

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