(📚) update docs to mention 3.11 support

[KotlinIsland]

• closes DOC: Update docs to indicate python 3.11 support #49301 (Replace xxxx with the GitHub issue number)
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations 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.

[lithomas1]

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.

[KotlinIsland]

TODO: Update 3.11-dev to 3.11 now that macOS has a release.

[KotlinIsland]

@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?

[lithomas1]

LGTM. Thanks for the PR!

[mroeschke]

Thanks @KotlinIsland

[lumberbot-app]

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.

[mroeschke]

@KotlinIsland mind following the instructions to submit a backport PR? (will need to target the 1.5.x branch)

[KotlinIsland]

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)

[KotlinIsland]

@mroeschke I found this

pandas/.github/workflows/sdist.yml

Line 33 in 46cb18c

python-version: ["3.8", "3.9", "3.10"]

and this

pandas/.github/workflows/sdist.yml

Lines 82 to 89 in 46cb18c

	case "${{matrix.python-version}}" in
	3.8)
	pip install numpy==1.20.3 ;;
	3.9)
	pip install numpy==1.20.3 ;;
	3.10)
	pip install numpy==1.21.2 ;;
	esac

Does this need to be updated to 3.11 as well?

[mroeschke]

Nice find @KotlinIsland, yeah it would be great to update that sdist build with 3.11 as well

[KotlinIsland]

#49460