Annotations tutorial

[timhoffm]

Three stylistic improvements

• Modify "Annotating an Artist" of Annotations tutorial

to a horizontal arrow so that the arrow line does not cross the
artist. This is somewhat special but visually more pleasing and
possibly a real use case.

old:

new:

• Change coordinates in Annotations tutorial

  ... in the transAxes / "axes fraction" example. Brining the
  annotations closer to the coordinate axes makes it easier to
  see that they are really the same. Also, the previous positioning
  (0.5, 0.5) without centered alignment results in almost, but not
  exactly centering of the text in the Axes frame, which is not
  quite nice visually.

old:

new:

• Modify "Annotating an Artist" of Annotations tutorial

  to a horizontal arrow so that the arrow line does not cross the
  artist. This is somewhat special but visually more pleasing and
  possibly a real use case.

old:

new:

[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 v3.7.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 73f3a8b59079b7e0cb8690b941b8ea3b8e4cd4fe

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

git commit -am 'Backport PR #25532: Annotations tutorial'

4. Push to a named branch:

git push YOURFORK v3.7.x:auto-backport-of-pr-25532-on-v3.7.x

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

"Backport PR #25532 on branch v3.7.x (Annotations tutorial)"

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.

[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 v3.7.1-doc
git pull

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

git cherry-pick -x -m1 73f3a8b59079b7e0cb8690b941b8ea3b8e4cd4fe

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

git commit -am 'Backport PR #25532: Annotations tutorial'

4. Push to a named branch:

git push YOURFORK v3.7.1-doc:auto-backport-of-pr-25532-on-v3.7.1-doc

5. Create a PR against branch v3.7.1-doc, I would have named this PR:

"Backport PR #25532 on branch v3.7.1-doc (Annotations tutorial)"

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.

[jklymak]

You can't really backport this in-situ because the tutorials moved. I guess you can decide if you want to backport manually to the old location, but maybe easier to just leave as a 3.8 improvement.