[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: I don't think that it's worth it to backport these changes, so I close the issue. Again, to avoid reintroducing such terms, I proposed https://github.com/python/devguide/issues/605 to define some general guidelines on the terminology. Thanks for reviews.

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: New changeset fbf43f051e7bf479709e122efa4b6edd4b09d4df by Victor Stinner in branch 'master': bpo-41521: Rename blacklist parameter to not_exported (GH-21824) https://github.com/python/cpython/commit/fbf43f051e7bf479709e122efa4b6edd4b09d4df -- _

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: > That said, I concur with Serhiy that there should be a discussion before > making a unilateral and stealthy change to the rules about how people are > allowed to write technical prose. I suggest you to join the discussion there: https://github.com/python/d

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Raymond Hettinger added the comment: > I would prefer avoiding python-dev, since there are many > trolls there who like to argue but not try to fix problem. It's not a good precedent to define as trolls anyone who might legitimately disagree, nor is it a good precedent to bypass discussion e

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: New changeset 20ae565bd2d79425d5567c001ed8f89848d7d907 by Victor Stinner in branch 'master': bpo-41521: Replace denylist with blocklist is http.cookiejar doc (GH-21826) https://github.com/python/cpython/commit/20ae565bd2d79425d5567c001ed8f89848d7d907 --

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: Serhiy: > Should not such changes be widely discussed on the Python-Dev mailing list > before merging? I would prefer avoiding python-dev, since there are many trolls there who like to argue but not try to fix problem. See the recent discussion about the PEP

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Łukasz Langa added the comment: New changeset 0e95bbf08571e98f4b688524efc2dcf20d315d91 by Victor Stinner in branch 'master': bpo-41521, typing: Rename _PROTO_WHITELIST to _PROTO_ALLOWLIST (#21825) https://github.com/python/cpython/commit/0e95bbf08571e98f4b688524efc2dcf20d315d91 -- no

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Serhiy Storchaka added the comment: Should not such changes be widely discussed on the Python-Dev mailing list before merging? -- nosy: +serhiy.storchaka ___ Python tracker _

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: Another rationale from "Inclusive Chromium code": Terms such as “blacklist” and “whitelist” reinforce the notion that black==bad and white==good. That Word Black, by Langston Hughes illustrates this problem in a lighthearted, if somewhat pointed way. These te

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: "While the etymology of the words isn't steeped in racial undertones or history like other problematic tech word choices, there is no harm in changing them to synonyms that as just as understandable and avoid the question entirely" https://web.archive.org/we

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Change by STINNER Victor : -- pull_requests: +20955 pull_request: https://github.com/python/cpython/pull/21826 ___ Python tracker ___ __

[issue41521] Replace whitelist/blacklist with allowlist/denylist

STINNER Victor added the comment: New changeset 0ee0b2938cb606151d8d287472c838044bad4a0e by Victor Stinner in branch 'master': bpo-41521: Replace whitelist/blacklist with allowlist/denylist (GH-21823) https://github.com/python/cpython/commit/0ee0b2938cb606151d8d287472c838044bad4a0e

[issue41521] Replace whitelist/blacklist with allowlist/denylist

miss-islington added the comment: New changeset fabd7bb8e0450f16ed5c5c0ad575aa413d65712d by Victor Stinner in branch 'master': bpo-41521: Replace whitelist/blacklist with allowlist/denylist (GH-21822) https://github.com/python/cpython/commit/fabd7bb8e0450f16ed5c5c0ad575aa413d65712d

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Change by STINNER Victor : -- pull_requests: +20954 pull_request: https://github.com/python/cpython/pull/21825 ___ Python tracker ___ __

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Change by STINNER Victor : -- pull_requests: +20953 pull_request: https://github.com/python/cpython/pull/21824 ___ Python tracker ___ __

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Christian Heimes added the comment: +1 -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Change by STINNER Victor : -- pull_requests: +20952 pull_request: https://github.com/python/cpython/pull/21823 ___ Python tracker ___ __

[issue41521] Replace whitelist/blacklist with allowlist/denylist

Change by STINNER Victor : -- keywords: +patch pull_requests: +20951 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21822 ___ Python tracker ___ _

[issue41521] Replace whitelist/blacklist with allowlist/denylist

New submission from STINNER Victor : 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 p