#17331 says that auto=True also changed, but there's no test for that here. Is that also fixed by this?

Not, sure will look at that tomorrow.

The auto keyword is about what state the autoscale is left in after setting the ylim, not if autoscaling should be merged with the current limits. That is, it controls if the next time you add an artist it will re-scale of if the limits are now fixed.

It is orthogonal to the bug, but I added a test for it while we are thinking about it (and added a symmetrical test of set_xlim)

I think you need to do the same for the set_zlim() for mplot3d? (or maybe it is taken care of through inheritance?)

The zlim does not participate in the lazy view lim setting 🤷‍♂️ so it was unaffected by this bug.

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 c7a6b12e103e582a3adb5960bd19f68489511ece

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

$ git commit -am 'Backport PR #17408: FIX: cancel pending autoscale on manually setting limits'

4. Push to a named branch :

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

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

"Backport PR #17408 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 to suggest an improvement.