Description

pochmann

opened on Dec 27, 2022

Issue body actions

Documentation

x or y is documented as:

if x is false, then y, else x

That looks unnatural/backwards/negated to me. It's not how I think of it. I suggest:

if x is true, then x, else y

Linked PRs

• gh-100556: Better or doc wording #100589
• [3.11] gh-100556: Improve clarity of or docs (GH-100589) #102108
• [3.10] gh-100556: Improve clarity of or docs (GH-100589) #102109

Activity

1. pochmann

   added

   docsDocumentation in the Doc dirDocumentation in the Doc dir

   on Dec 27, 2022
2. erlend-aasland

   added a commit that references this issue on Feb 21, 2023

   gh-100556: Improve clarity of `or` docs (#100589)

   b40dd71
3. miss-islington

   added 2 commits that reference this issue on Feb 21, 2023

   pythongh-100556: Improve clarity of `or` docs (pythonGH-100589)

   57ba8e6

   pythongh-100556: Improve clarity of `or` docs (pythonGH-100589)

   4c9a446
4. erlend-aasland

   closed this as completedon Feb 21, 2023
5. miss-islington

   added 2 commits that reference this issue on Feb 21, 2023

   gh-100556: Improve clarity of `or` docs (GH-100589)

   444ec74

   gh-100556: Improve clarity of `or` docs (GH-100589)

   a94f3ad
6. carljm

   added a commit that references this issue on Feb 23, 2023

   Merge branch 'main' into lockfreecp

   b257a16
7. python-sidebar

   added 2 commits that reference this issue on Sep 1, 2024

   pythongh-100556: Improve clarity of `or` docs (python#100589)

   9fb4ef8

   pythongh-100556: Improve clarity of `or` docs (python#100589)

   75260af
8. JelleZijlstra

   added a commit that references this issue on Sep 10, 2024

   pythongh-100556: Improve clarity of `or` docs (python#100589)

   3d5a88e

Issue actions