RST markup: recommend anonymous hyperlinks

contrib/intro/index.rst

@@ -24,12 +24,12 @@ Python is an open source project, with culture and techniques from the broader
 open source world.  You might find it helpful to read about open source in
 general.  A number of individuals from the Python community have contributed to
 a series of excellent guides at `Open Source Guides
-<https://opensource.guide/>`_.
+<https://opensource.guide/>`__.
 
 Anyone will find the following guides useful:
 
-* `How to Contribute to Open Source <https://opensource.guide/how-to-contribute/>`_
-* `Building Welcoming Communities <https://opensource.guide/building-community/>`_
+* `How to Contribute to Open Source <https://opensource.guide/how-to-contribute/>`__
+* `Building Welcoming Communities <https://opensource.guide/building-community/>`__
 
 
 Healthy collaboration

core-team/committing.rst

@@ -59,11 +59,11 @@ to enter the public source tree. Ask yourself the following questions:
 
 * **Does the pull request pass a check indicating that the submitter has signed the CLA?**
    Make sure that the contributor has signed a `Contributor
-   Licensing Agreement <https://www.python.org/psf/contrib/contrib-form/>`_
+   Licensing Agreement <https://www.python.org/psf/contrib/contrib-form/>`__
    (CLA), unless their change has no possible intellectual property
    associated with it (for example, fixing a spelling mistake in documentation).
    The `Python Software Foundation Contributor License Agreement Management Bot
-   <https://github.com/psf/clabot>`_
+   <https://github.com/psf/clabot>`__
    checks whether the author has signed the CLA, and replies in the PR
    if they haven't. For further questions about the CLA
    process, write to [email protected].
@@ -125,7 +125,7 @@ How to add a NEWS entry
 ^^^^^^^^^^^^^^^^^^^^^^^
 
 ``NEWS`` entries go into the ``Misc/NEWS.d`` directory as individual files. The
-``NEWS`` entry can be created by using `blurb-it <https://blurb-it.herokuapp.com/>`_,
+``NEWS`` entry can be created by using `blurb-it <https://blurb-it.herokuapp.com/>`__,
 or the :pypi:`blurb` tool and its ``blurb add`` command.
 
 If you are unable to use the tool, then you can create the ``NEWS`` entry file

core-team/experts.rst

@@ -365,6 +365,6 @@ Documentation translations
 ==========================
 
 Translations are within the charter of
-`Editorial Board <https://python.github.io/editorial-board/>`_.
+`Editorial Board <https://python.github.io/editorial-board/>`__.
 For a list of translations and their coordinators, see
 :ref:`this table of translations <translation-coordinators>`.

core-team/join-team.rst

@@ -40,27 +40,27 @@ are granted through these steps:
    (as per :pep:`13`), the submitter `emails the steering council
    <mailto:[email protected]>`_ with the candidate's email address
    requesting that the council either accept or reject the proposed membership.  Technically, the
-   council may only `veto a positive vote <https://peps.python.org/pep-0013/#membership>`_.
+   council may only `veto a positive vote <https://peps.python.org/pep-0013/#membership>`__.
 
 #. Assuming the steering council does not veto the positive vote, a member of the council or its
    delegate (approver, usually in practice a :ref:`Developer-in-Residence <current owners>`) will
    email the candidate:
 
    - A request for account details as required by
-     `🔒 python/voters <https://github.com/python/voters>`_.
+     `🔒 python/voters <https://github.com/python/voters>`__.
    - A reminder about the `Code of Conduct`_ and guidance on reporting issues
      to the PSF Conduct WG.
 
 #. Once the candidate has provided the pertinent details, the approver will:
 
    - Enable the various new privileges.
    - Remove the new committer from the triage team, if applicable.
-   - Add their details to `🔒 python/voters <https://github.com/python/voters>`_.
+   - Add their details to `🔒 python/voters <https://github.com/python/voters>`__.
    - Once the python/voters update is merged, regenerate the public team membership
      list at :ref:`developers`.
      See "Public list of members" in the ``voters`` README.
    - Post an announcement in the `Committers Discourse category
-     <https://discuss.python.org/c/committers/5>`_.  The past few announcements
+     <https://discuss.python.org/c/committers/5>`__.  The past few announcements
      were in the form of a separate post on the already open topic with
      the poll.
 
@@ -69,7 +69,7 @@ Getting a python.org email address
 
 Members of the core team can get an email address on the python.org domain.
 For more details refer to the `python.org email policy
-<https://www.python.org/psf/records/board/policies/email/>`_.
+<https://www.python.org/psf/records/board/policies/email/>`__.
 
 
 Poll template

core-team/memorialization.rst

@@ -31,29 +31,29 @@ certain content when the legacy contact or family members request it.
 GitHub
 ------
 
-* The user is removed from the `python/ <https://github.com/orgs/python/>`_
+* The user is removed from the `python/ <https://github.com/orgs/python/>`__
   organization on GitHub;
-* The user is removed from the `psf/ <https://github.com/orgs/psf/>`_
+* The user is removed from the `psf/ <https://github.com/orgs/psf/>`__
   organization on GitHub;
-* The user is removed from the `pypa/ <https://github.com/orgs/pypa/>`_
+* The user is removed from the `pypa/ <https://github.com/orgs/pypa/>`__
   organization on GitHub.
 
 The PSF staff does not follow up with GitHub with regards to GitHub account
 cancellation as this action is reserved for next-of-kin or designated by
 the deceased GitHub user to act as an account successor.
 
 The general policy regarding deceased users on GitHub is described on their
-`Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
+`Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`__
 page.
 
 Repositories in the organization
 --------------------------------
 
 * The user's GitHub handle is removed from ``/.github/CODEOWNERS``.
   To see all that need action, perform
-  `this query <https://github.com/search?q=org%3Apython+path%3A**%2F.github%2FCODEOWNERS+USERNAME&type=code>`_.
+  `this query <https://github.com/search?q=org%3Apython+path%3A**%2F.github%2FCODEOWNERS+USERNAME&type=code>`__.
 * The user is marked as deceased in the private
-  `voters/python-core.toml <https://github.com/python/voters/blob/main/python-core.toml>`_
+  `voters/python-core.toml <https://github.com/python/voters/blob/main/python-core.toml>`__
   file with the ``left=`` field set to the day of passing, if known.
 
 discuss.python.org
@@ -80,7 +80,7 @@ a community member close to the deceased.
 
 The general best practice for deceased community members on
 Discourse-powered forums is described on their
-`Best practices for deceased community members <https://meta.discourse.org/t/best-practices-for-deceased-community-members/146210>`_
+`Best practices for deceased community members <https://meta.discourse.org/t/best-practices-for-deceased-community-members/146210>`__
 page.
 
 python.org email account
@@ -116,8 +116,8 @@ python.org admin
 devguide.python.org
 -------------------
 
-* The user is marked as deceased in `core-team.csv <https://github.com/python/devguide/blob/main/core-team/core-team.csv>`_;
-* The user is removed from the `experts index <https://github.com/python/devguide/blob/main/core-team/experts.rst>`_.
+* The user is marked as deceased in `core-team.csv <https://github.com/python/devguide/blob/main/core-team/core-team.csv>`__;
+* The user is removed from the `experts index <https://github.com/python/devguide/blob/main/core-team/experts.rst>`__.
 
 bugs.python.org
 ---------------
@@ -139,16 +139,16 @@ Other PSF-related infrastructure
   Discord server to remove the user from the server. The PSF staff
   does not follow up with Discord with regards to Discord account
   cancellation. The general policy regarding deceased users on Discord
-  is available on their `Deceased or Incapacitated Users <https://support.discord.com/hc/en-us/articles/19872987802263--Deceased-or-Incapacitated-Users>`_
+  is available on their `Deceased or Incapacitated Users <https://support.discord.com/hc/en-us/articles/19872987802263--Deceased-or-Incapacitated-Users>`__
   page.
 
 * The user is removed from Salt configuration for the PSF infrastructure
-  in `/pillar/base/users <https://github.com/python/psf-salt/tree/main/pillar/base/users>`_
+  in `/pillar/base/users <https://github.com/python/psf-salt/tree/main/pillar/base/users>`__
   that allows SSH access to PSF-controlled servers.
 
 * The user might have ran a buildbot worker. The PSF staff member will
   look for that in the
-  `buildmaster-config <https://github.com/search?q=repo%3Apython%2Fbuildmaster-config%20USERNAME&type=code>`_
+  `buildmaster-config <https://github.com/search?q=repo%3Apython%2Fbuildmaster-config%20USERNAME&type=code>`__
   repository.
 
 PyPI

core-team/motivations.rst

@@ -97,13 +97,13 @@ participating in the CPython core development process:
 
 .. topic:: Brett Cannon (Canada)
 
-   * Personal site: `snarky.ca <https://snarky.ca/>`_
+   * Personal site: `snarky.ca <https://snarky.ca/>`__
    * Microsoft (Software Developer)
    * Python Software Foundation (Fellow)
 
 .. topic:: Alyssa Coghlan (Australia)
 
-   * Personal site: `Curious Efficiency <https://www.curiousefficiency.org/>`_
+   * Personal site: `Curious Efficiency <https://www.curiousefficiency.org/>`__
    * `Extended bio <https://www.curiousefficiency.org/pages/about>`__
    * Python Software Foundation (Fellow, Packaging Working Group)
    * Westpac (Principal Python Engineer)
@@ -123,9 +123,9 @@ participating in the CPython core development process:
 .. topic:: Steve Dower (United States/Australia)
 
    * Microsoft (Software Developer)
-   * Personal site: `stevedower.id.au <https://stevedower.id.au/>`_
-   * Speaking: `stevedower.id.au/speaking <https://stevedower.id.au/speaking>`_
-   * Work blog: `devblogs.microsoft.com/python/ <https://devblogs.microsoft.com/python/>`_
+   * Personal site: `stevedower.id.au <https://stevedower.id.au/>`__
+   * Speaking: `stevedower.id.au/speaking <https://stevedower.id.au/speaking>`__
+   * Work blog: `devblogs.microsoft.com/python/ <https://devblogs.microsoft.com/python/>`__
    * Email address: [email protected]
 
    Steve started with Python while automating a test harness for medical
@@ -143,25 +143,25 @@ participating in the CPython core development process:
 
 .. topic:: Mariatta (Canada)
 
-   * Personal site: `mariatta.ca <https://mariatta.ca>`_
-   * Works as a `Software Engineer <https://www.linkedin.com/in/mariatta/>`_
+   * Personal site: `mariatta.ca <https://mariatta.ca>`__
+   * Works as a `Software Engineer <https://www.linkedin.com/in/mariatta/>`__
      in Vancouver, helps organize `Vancouver PyLadies
-     <https://www.meetup.com/PyLadies-Vancouver/>`_ meetup on the side, and
-     sometimes `speaks <https://mariatta.ca/posts/talks/>`_
+     <https://www.meetup.com/PyLadies-Vancouver/>`__ meetup on the side, and
+     sometimes `speaks <https://mariatta.ca/posts/talks/>`__
      at conferences.
    * Email address: [email protected]
-   * `Sponsor Mariatta on GitHub <https://github.com/sponsors/Mariatta>`_
-   * `Patreon <https://www.patreon.com/Mariatta>`_
+   * `Sponsor Mariatta on GitHub <https://github.com/sponsors/Mariatta>`__
+   * `Patreon <https://www.patreon.com/Mariatta>`__
 
-   Support Mariatta by `becoming a sponsor <https://github.com/sponsors/Mariatta>`_,
-   sending her a `happiness packet <https://www.happinesspackets.io/send/>`_,
-   or `paypal <https://www.paypal.com/paypalme/mariatta>`_.
+   Support Mariatta by `becoming a sponsor <https://github.com/sponsors/Mariatta>`__,
+   sending her a `happiness packet <https://www.happinesspackets.io/send/>`__,
+   or `paypal <https://www.paypal.com/paypalme/mariatta>`__.
 
 .. topic:: R. David Murray (United States)
 
-   * Personal site: `bitdance.com <https://www.bitdance.com>`_
+   * Personal site: `bitdance.com <https://www.bitdance.com>`__
    * Available for `Python and Internet Services Consulting
-     and Python contract programming <https://www.murrayandwalker.com/>`_
+     and Python contract programming <https://www.murrayandwalker.com/>`__
 
    David has been involved in the Internet since the days when the old IBM
    BITNET and the ARPANet got cross connected, and in Python programming since
@@ -177,7 +177,7 @@ participating in the CPython core development process:
 
    David currently does both proprietary and open source development work,
    primarily in Python, through the company in which he is a partner, `Murray &
-   Walker, Inc <https://www.murrayandwalker.com>`_.  He has done contract work
+   Walker, Inc <https://www.murrayandwalker.com>`__.  He has done contract work
    focused specifically on CPython development both through the PSF (the
    kickstart of the email Unicode API development) and directly funded by
    interested corporations (additional development work on email funded by
@@ -187,7 +187,7 @@ participating in the CPython core development process:
 
 .. topic:: Antoine Pitrou (France)
 
-   * LinkedIn: `<https://www.linkedin.com/in/pitrou/>`_ (Senior Software Engineer)
+   * LinkedIn: `<https://www.linkedin.com/in/pitrou/>`__ (Senior Software Engineer)
    * QuantStack
    * Python Software Foundation (Fellow)
    * Email address: [email protected]
@@ -213,7 +213,7 @@ participating in the CPython core development process:
 
    Victor is paid by Red Hat to maintain Python upstream and downstream (RHEL,
    CentOS, Fedora & Software collections). See `Victor's contributions to
-   Python <https://vstinner.readthedocs.io/python_contrib.html>`_.
+   Python <https://vstinner.readthedocs.io/python_contrib.html>`__.
 
 .. topic:: Kushal Das (India)
 
@@ -224,21 +224,21 @@ participating in the CPython core development process:
 .. topic:: Barry Warsaw (United States)
 
    * NVIDIA, Principal System Software Engineer, Open Source Python Ecosystem
-   * Personal site: `barry.warsaw.us <https://barry.warsaw.us/>`_
-   * Blog: `We Fear Change <https://www.wefearchange.org/>`_
-   * `LinkedIn <https://www.linkedin.com/in/barry-warsaw/>`_
-   * `Bluesky <https://bsky.app/profile/pumpichank.bsky.social>`_
+   * Personal site: `barry.warsaw.us <https://barry.warsaw.us/>`__
+   * Blog: `We Fear Change <https://www.wefearchange.org/>`__
+   * `LinkedIn <https://www.linkedin.com/in/barry-warsaw/>`__
+   * `Bluesky <https://bsky.app/profile/pumpichank.bsky.social>`__
    * Email address: [email protected]
    * Python Software Foundation (Fellow)
 
    Barry has been working in, with, and on Python since 1994.  He attended the
-   first Python workshop at `NIST <https://www.nist.gov/>`_ in Gaithersburg,
+   first Python workshop at `NIST <https://www.nist.gov/>`__ in Gaithersburg,
    MD in 1994, where he met Guido and several other early Python adopters.
    Barry subsequently worked with Guido for 8 years while at `CNRI
-   <http://cnri.reston.va.us/>`_.  Barry has served as Python's postmaster,
+   <http://cnri.reston.va.us/>`__.  Barry has served as Python's postmaster,
    webmaster, release manager, Language Summit co-chair, `Jython
-   <https://www.jython.org/>`_ project leader, `GNU Mailman
-   <https://www.list.org/>`_ project leader, and Python Steering Council
+   <https://www.jython.org/>`__ project leader, `GNU Mailman
+   <https://www.list.org/>`__ project leader, and Python Steering Council
    member in 2019, 2020, 2021, 2024, and 2025.
 
 .. topic:: Eric Snow (United States)
@@ -256,13 +256,13 @@ participating in the CPython core development process:
    developers on the project for 6 years.  After that he started the Python
    Tools for Visual Studio project focusing on providing advanced code completion
    and debugging features for Python.  Today he works on
-   `Cinder <https://github.com/facebookincubator/cinder/>`_ improving Python
+   `Cinder <https://github.com/facebookincubator/cinder/>`__ improving Python
    performance for Instagram.
 
 .. topic:: Carol Willing (United States)
 
    * Noteable (VP Engineering)
-   * Personal site: `Willing Consulting <https://www.willingconsulting.com/>`_
+   * Personal site: `Willing Consulting <https://www.willingconsulting.com/>`__
    * `Extended bio <https://www.willingconsulting.com/about/>`__
    * Project Jupyter (Software Council, Core Team for JupyterHub/Binder)
    * Python Software Foundation (Fellow)

core-team/responsibilities.rst

@@ -48,12 +48,12 @@ Communication channels and bug notifications
 ============================================
 
 Mailing lists have generally been replaced by the
-`Discourse forum <https://discuss.python.org/>`_ (``discuss.python.org``).
+`Discourse forum <https://discuss.python.org/>`__ (``discuss.python.org``).
 Refer to the :ref:`mailinglists` and :ref:`communication-discourse` sections
 for more information.
 
 If you want notification of new issues, you can use the appropriate GitHub notification
-settings for the `python/cpython <https://github.com/python/cpython>`_ repository —
+settings for the `python/cpython <https://github.com/python/cpython>`__ repository —
 follow the link and click on the :guilabel:`Watch` button to set your notification options.
 
 

developer-workflow/c-api.rst

@@ -38,7 +38,7 @@ While internal API can be changed at any time, it's still good to keep it
 stable: other API or other CPython developers may depend on it.
 For users, internal API is sometimes the best workaround for a thorny problem
 --- though those use cases should be discussed on the
-`C API Discourse category <https://discuss.python.org/c/30>`_
+`C API Discourse category <https://discuss.python.org/c/30>`__
 or an issue so we can try to find a supported way to serve them.
 
 
@@ -218,7 +218,7 @@ use this API reliably:
   (:samp:`3.{x}.0`, including Alphas and Betas for :samp:`3.{x}.0`).
 * Adding a new unstable API *for an existing feature* is allowed even after
   Beta feature freeze, up until the first Release Candidate.
-  Consensus on the `Core Development Discourse <https://discuss.python.org/c/core-dev/23>`_
+  Consensus on the `Core Development Discourse <https://discuss.python.org/c/core-dev/23>`__
   is needed in the Beta period.
 * Backwards-incompatible changes should make existing C callers fail to compile.
   For example, arguments should be added/removed, or a function should be