(📚) update docs to mention 3.11 support
State: closed

- [x] closes #49301 (Replace xxxx with the GitHub issue number)
- [ ] [Tests added and passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests) if fixing a bug or adding a new feature
- [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
- [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
- [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.


Labels:
name: Docs

Comments:
Can you add a line below https://github.com/pandas-dev/pandas/blame/main/setup.cfg#L25 for Python 3.11, and also below https://github.com/pandas-dev/pandas/blame/main/setup.cfg#L25 (where Python 3.11 would install numpy 1.23.2)?

I think we also need to bump oldest-supported-numpy to >= 2022.8.16 here https://github.com/pandas-dev/pandas/blob/main/pyproject.toml#L8. 

Sorry for the mess, I overlooked this when I added the initial support. Let me know if you have any other questions.
TODO: Update `3.11-dev` to `3.11` now that macOS has a release.
@lithomas1 

> Can you add a line below https://github.com/pandas-dev/pandas/blame/main/setup.cfg#L25 for Python 3.11

I have already added a trove classifier for 3.11 in setup.cfg.

> , and also below https://github.com/pandas-dev/pandas/blame/main/setup.cfg#L25 (where Python 3.11 would install numpy 1.23.2)?

This is the same link as before, did you mean in the `install_requires` section? I've updated this.

Want to take another look now?


Thanks @KotlinIsland 
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.5.x
git pull
```

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

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

```
git commit -am 'Backport PR #49320: (📚) update docs to mention 3.11 support'
```

4. Push to a named branch:

```
git push YOURFORK 1.5.x:auto-backport-of-pr-49320-on-1.5.x
```

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

> "Backport PR #49320 on branch 1.5.x ((📚) update docs to mention 3.11 support)"

And apply the correct labels and milestones.

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

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

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                
@KotlinIsland mind following the instructions to submit a backport PR? (will need to target the 1.5.x branch) 
Attention rick-and-morty bot, I have done it! I have done some good work! I wonder if I will turn into a Pickle! I'll be Pickle-KotlinIsland!!!!! (#49440)
@mroeschke I found this 

https://github.com/pandas-dev/pandas/blob/46cb18c4a021f5058f9018aa9c3106cfc7914aa7/.github/workflows/sdist.yml#L33

and this

https://github.com/pandas-dev/pandas/blob/46cb18c4a021f5058f9018aa9c3106cfc7914aa7/.github/workflows/sdist.yml#L82-L89

Does this need to be updated to 3.11 as well?
Nice find @KotlinIsland, yeah it would be great to update that sdist build with 3.11 as well 
#49460