API: Treat 1D vectors as columns in some cases for arith/cmp ops #23306
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Definitely needs discussion.
There are a bunch of GH issues (will track down the list in a bit) that boil down to users expecting DataFrame+(Series|ndarray|listlike) ops to operate column-by-column. This PR implements that behavior for a subset of cases. In particular:
other
is aSeries
: indexes match exactly (and columns do not)other
is a list/tuple/np.ndarray: length matches df.index (and not df.columns)This means that things like
df == df['A']
will now work.git diff upstream/master -u -- "*.py" | flake8 --diff