You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
``NEWS`` entries go into the ``Misc/NEWS.d`` directory as individual files. The
128
-
``NEWS`` entry can be created by using `blurb-it <https://blurb-it.herokuapp.com/>`_,
128
+
``NEWS`` entry can be created by using `blurb-it <https://blurb-it.herokuapp.com/>`__,
129
129
or the :pypi:`blurb` tool and its ``blurb add`` command.
130
130
131
131
If you are unable to use the tool, then you can create the ``NEWS`` entry file
requesting that the council either accept or reject the proposed membership. Technically, the
43
-
council may only `veto a positive vote <https://peps.python.org/pep-0013/#membership>`_.
43
+
council may only `veto a positive vote <https://peps.python.org/pep-0013/#membership>`__.
44
44
45
45
#. Assuming the steering council does not veto the positive vote, a member of the council or its
46
46
delegate (approver, usually in practice a :ref:`Developer-in-Residence <current owners>`) will
Copy file name to clipboardExpand all lines: core-team/memorialization.rst
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,29 +31,29 @@ certain content when the legacy contact or family members request it.
31
31
GitHub
32
32
------
33
33
34
-
* The user is removed from the `python/ <https://github.com/orgs/python/>`_
34
+
* The user is removed from the `python/ <https://github.com/orgs/python/>`__
35
35
organization on GitHub;
36
-
* The user is removed from the `psf/ <https://github.com/orgs/psf/>`_
36
+
* The user is removed from the `psf/ <https://github.com/orgs/psf/>`__
37
37
organization on GitHub;
38
-
* The user is removed from the `pypa/ <https://github.com/orgs/pypa/>`_
38
+
* The user is removed from the `pypa/ <https://github.com/orgs/pypa/>`__
39
39
organization on GitHub.
40
40
41
41
The PSF staff does not follow up with GitHub with regards to GitHub account
42
42
cancellation as this action is reserved for next-of-kin or designated by
43
43
the deceased GitHub user to act as an account successor.
44
44
45
45
The general policy regarding deceased users on GitHub is described on their
46
-
`Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`_
46
+
`Deceased User Policy <https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy>`__
47
47
page.
48
48
49
49
Repositories in the organization
50
50
--------------------------------
51
51
52
52
* The user's GitHub handle is removed from ``/.github/CODEOWNERS``.
file with the ``left=`` field set to the day of passing, if known.
58
58
59
59
discuss.python.org
@@ -80,7 +80,7 @@ a community member close to the deceased.
80
80
81
81
The general best practice for deceased community members on
82
82
Discourse-powered forums is described on their
83
-
`Best practices for deceased community members <https://meta.discourse.org/t/best-practices-for-deceased-community-members/146210>`_
83
+
`Best practices for deceased community members <https://meta.discourse.org/t/best-practices-for-deceased-community-members/146210>`__
84
84
page.
85
85
86
86
python.org email account
@@ -116,8 +116,8 @@ python.org admin
116
116
devguide.python.org
117
117
-------------------
118
118
119
-
* The user is marked as deceased in `core-team.csv <https://github.com/python/devguide/blob/main/core-team/core-team.csv>`_;
120
-
* The user is removed from the `experts index <https://github.com/python/devguide/blob/main/core-team/experts.rst>`_.
119
+
* The user is marked as deceased in `core-team.csv <https://github.com/python/devguide/blob/main/core-team/core-team.csv>`__;
120
+
* The user is removed from the `experts index <https://github.com/python/devguide/blob/main/core-team/experts.rst>`__.
121
121
122
122
bugs.python.org
123
123
---------------
@@ -139,16 +139,16 @@ Other PSF-related infrastructure
139
139
Discord server to remove the user from the server. The PSF staff
140
140
does not follow up with Discord with regards to Discord account
141
141
cancellation. The general policy regarding deceased users on Discord
142
-
is available on their `Deceased or Incapacitated Users <https://support.discord.com/hc/en-us/articles/19872987802263--Deceased-or-Incapacitated-Users>`_
142
+
is available on their `Deceased or Incapacitated Users <https://support.discord.com/hc/en-us/articles/19872987802263--Deceased-or-Incapacitated-Users>`__
143
143
page.
144
144
145
145
* The user is removed from Salt configuration for the PSF infrastructure
146
-
in `/pillar/base/users <https://github.com/python/psf-salt/tree/main/pillar/base/users>`_
146
+
in `/pillar/base/users <https://github.com/python/psf-salt/tree/main/pillar/base/users>`__
147
147
that allows SSH access to PSF-controlled servers.
148
148
149
149
* The user might have ran a buildbot worker. The PSF staff member will
* Work blog: `devblogs.microsoft.com/python/ <https://devblogs.microsoft.com/python/>`_
126
+
* Personal site: `stevedower.id.au <https://stevedower.id.au/>`__
* Work blog: `devblogs.microsoft.com/python/ <https://devblogs.microsoft.com/python/>`__
Barry has been working in, with, and on Python since 1994. He attended the
235
-
first Python workshop at `NIST <https://www.nist.gov/>`_ in Gaithersburg,
235
+
first Python workshop at `NIST <https://www.nist.gov/>`__ in Gaithersburg,
236
236
MD in 1994, where he met Guido and several other early Python adopters.
237
237
Barry subsequently worked with Guido for 8 years while at `CNRI
238
-
<http://cnri.reston.va.us/>`_. Barry has served as Python's postmaster,
238
+
<http://cnri.reston.va.us/>`__. Barry has served as Python's postmaster,
239
239
webmaster, release manager, Language Summit co-chair, `Jython
Copy file name to clipboardExpand all lines: developer-workflow/c-api.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ While internal API can be changed at any time, it's still good to keep it
38
38
stable: other API or other CPython developers may depend on it.
39
39
For users, internal API is sometimes the best workaround for a thorny problem
40
40
--- though those use cases should be discussed on the
41
-
`C API Discourse category <https://discuss.python.org/c/30>`_
41
+
`C API Discourse category <https://discuss.python.org/c/30>`__
42
42
or an issue so we can try to find a supported way to serve them.
43
43
44
44
@@ -218,7 +218,7 @@ use this API reliably:
218
218
(:samp:`3.{x}.0`, including Alphas and Betas for :samp:`3.{x}.0`).
219
219
* Adding a new unstable API *for an existing feature* is allowed even after
220
220
Beta feature freeze, up until the first Release Candidate.
221
-
Consensus on the `Core Development Discourse <https://discuss.python.org/c/core-dev/23>`_
221
+
Consensus on the `Core Development Discourse <https://discuss.python.org/c/core-dev/23>`__
222
222
is needed in the Beta period.
223
223
* Backwards-incompatible changes should make existing C callers fail to compile.
224
224
For example, arguments should be added/removed, or a function should be
0 commit comments