REGR: spearman corr raising on 32-bit
State: closed

- [x] closes #43588
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit) for how to run them
- [x] whatsnew entry

This works on master, so this PR just adds a regression test (by removing the unnecessary `scipy` skips, this should be ensuring that some `spearman` tests will be run on 32-bit).

In the backport, these tests with the skip removed should fail, but the fix should be tiny (replacing 2 `int64` with `intp`)

Labels:
name: Regression
description: Functionality that used to work in a prior pandas version
name: Numeric Operations
description: Arithmetic, Comparison, and Logical operations
name: 32bit
description: 32-bit systems

Comments:
> In the backport, these tests with the skip removed should fail, but the fix should be tiny (replacing 2 int64 with intp)

ok @mzeitlin11 merge then fixup the backport right?
> > In the backport, these tests with the skip removed should fail, but the fix should be tiny (replacing 2 int64 with intp)
> 
> ok @mzeitlin11 merge then fixup the backport right?

Yep!
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
$ git checkout 1.3.x
$ git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
$ git cherry-pick -m1 6791678b19513748441c120c697ae33d74802447
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
$ git commit -am 'Backport PR #43608: REGR: spearman corr raising on 32-bit'
```

4. Push to a named branch :

```
git push YOURFORK 1.3.x:auto-backport-of-pr-43608-on-1.3.x
```

5. Create a PR against branch 1.3.x, I would have named this PR:

> "Backport PR #43608 on branch 1.3.x (REGR: spearman corr raising on 32-bit)"

And apply the correct labels and milestones.

Congratulation you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove `Still Needs Manual Backport` label once the PR gets merged.

If these instruction are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
@meeseeksdev backport 1.3.x
Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
$ git checkout 1.3.x
$ git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
$ git cherry-pick -m1 6791678b19513748441c120c697ae33d74802447
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
$ git commit -am 'Backport PR #43608: REGR: spearman corr raising on 32-bit'
```

4. Push to a named branch :

```
git push YOURFORK 1.3.x:auto-backport-of-pr-43608-on-1.3.x
```

5. Create a PR against branch 1.3.x, I would have named this PR:

> "Backport PR #43608 on branch 1.3.x (REGR: spearman corr raising on 32-bit)"

And apply the correct labels and milestones.

Congratulation you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove `Still Needs Manual Backport` label once the PR gets merged.

If these instruction are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).