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.2.x$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 3f78c1a7c61de377f682e30b872bf77a6a094467

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

$ git commit -am 'Backport PR #17043: Avoid spurious deprecation warning in TextBox.'

4. Push to a named branch :

git push YOURFORK v3.2.x:auto-backport-of-pr-17043-on-v3.2.x

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

"Backport PR#17043 on branch v3.2.x"

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!

If these instruction are inaccurate, feel free tosuggest an improvement.

Does not need backporting. The offendingrc_context was introduced later, v3.2.x still manually sets and resets rcParams instead.