Thanks @myzhang1029

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 v3.11.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 d421cec6b6212480bd172678b914647b2bc178a2

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

git commit -am 'Backport PR #31884: MNT: add `@classmethod` and remove `ignore` post #31867'

4. Push to a named branch:

git push YOURFORK v3.11.x:auto-backport-of-pr-31884-on-v3.11.x

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

"Backport PR #31884 on branch v3.11.x (MNT: add @classmethod and remove ignore post #31867)"

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.

I haven’t checked why The backport fails. Anyway, it’s not worth spending time on since this only fixes a comment.