[3.14] gh-141650: Fix typo in xml.sax.saxutils.unescape documentation (GH-141652)

[miss-islington]

(cherry picked from commit df8091d)

Co-authored-by: Tamzin Hadasa Kelly tk.infinity@gmail.com

• Issue: Typo in saxutils docs #141650

---

📚 Documentation preview 📚: https://cpython-previews--141654.org.readthedocs.build/

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[hugovk]

@TamzinHadasa Please could you sign the CLA again?

See https://devguide.python.org/getting-started/pull-request-lifecycle/#why-do-i-need-to-sign-the-cla-again

[TamzinHadasa]

@hugovk I never make commits from that email address, which is just my go-to "send spam here" Gmail from childhood. I'm happy to re-sign the CLA with it if that's necessary, but wouldn't want that to be the commit email of record. Do I need to change something in my GitHub account settings?

[hugovk]

GitHub already used the email from your account when the original PR was squashed. We can confirm by running:

git show df8091d516f874bd8222569794229ea77fb3a0a3

Or looking at:

https://github.com/python/cpython/commit/df8091d516f874bd8222569794229ea77fb3a0a3.patch

Yes, it is necessary to sign the CLA with that email to be able to merge these backports, and it doesn't change that this email was already used for the original squash-merge.

You can change your GitHub settings if you want, which would affect what address is used for squash-merged commits in the future.

(Personally I use the private @users.noreply.github.com email locally and via the GitHub settings.)

[TamzinHadasa]

Huh. Well I'll look into that on my end. Signed now. 🙂

[hugovk]

Thank you!