New submission from STINNER Victor <vstinner@python.org>:
I propose to replace whitelist/blacklist with allowlist/denylist. The terms whitelist and blacklist can be associated to color skins which isn't the intent. To avoid confusion, I propose to use neutral terms: allowlist and denylist. Moreover, as a french person (english is not my first language, but french), "allow" and "deny" are even more explicit to me than "white "and "black".
The intent is to make the Python community more welcoming and more diverse by avoiding to make some people uncomfortable.
Many other projects already replaced whitelist/blacklist with allowlist/denylist:
* GitLab: https://gitlab.com/gitlab-org/gitlab/-/issues/7554
* React: https://github.com/facebook/react/commit/8a8d973d3cc5623676a84f87af66ef9259c3937c
* Mediawiki: https://phabricator.wikimedia.org/T254646
* GitHub: https://thenextweb.com/dd/2020/06/15/github-plans-to-replace-racially-insensitive-terms-like-master-and-whitelist/
* Google Chrome: https://9to5google.com/2020/06/12/google-android-chrome-blacklist-blocklist-more-inclusive/
* etc.
See also:
* Carolyn Stransky's "Humanizing Your Documentation" presentation:
https://speakerdeck.com/carolstran/humanizing-your-documentation-full-talk
* bpo-34605: "Avoid master/slave terminology"
Attached PRs replace whitelist/blacklist with allowlist/denylist.
----------
assignee: docs@python
components: Documentation, Library (Lib)
messages: 375170
nosy: docs@python, vstinner
priority: normal
severity: normal
status: open
title: Replace whitelist/blacklist with allowlist/denylist
versions: Python 3.10
_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue41521>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
I propose to replace whitelist/blacklist with allowlist/denylist. The terms whitelist and blacklist can be associated to color skins which isn't the intent. To avoid confusion, I propose to use neutral terms: allowlist and denylist. Moreover, as a french person (english is not my first language, but french), "allow" and "deny" are even more explicit to me than "white "and "black".
The intent is to make the Python community more welcoming and more diverse by avoiding to make some people uncomfortable.
Many other projects already replaced whitelist/blacklist with allowlist/denylist:
* GitLab: https://gitlab.com/gitlab-org/gitlab/-/issues/7554
* React: https://github.com/facebook/react/commit/8a8d973d3cc5623676a84f87af66ef9259c3937c
* Mediawiki: https://phabricator.wikimedia.org/T254646
* GitHub: https://thenextweb.com/dd/2020/06/15/github-plans-to-replace-racially-insensitive-terms-like-master-and-whitelist/
* Google Chrome: https://9to5google.com/2020/06/12/google-android-chrome-blacklist-blocklist-more-inclusive/
* etc.
See also:
* Carolyn Stransky's "Humanizing Your Documentation" presentation:
https://speakerdeck.com/carolstran/humanizing-your-documentation-full-talk
* bpo-34605: "Avoid master/slave terminology"
Attached PRs replace whitelist/blacklist with allowlist/denylist.
----------
assignee: docs@python
components: Documentation, Library (Lib)
messages: 375170
nosy: docs@python, vstinner
priority: normal
severity: normal
status: open
title: Replace whitelist/blacklist with allowlist/denylist
versions: Python 3.10
_______________________________________
Python tracker <report@bugs.python.org>
<https://bugs.python.org/issue41521>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com