-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-102105 Fix wording in filterfalse/quantify/filter #102189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -398,7 +398,7 @@ loops that truncate the stream. | |||
.. function:: filterfalse(predicate, iterable) | |||
|
|||
Make an iterator that filters elements from iterable returning only those for | |||
which the predicate is ``False``. If *predicate* is ``None``, return the items | |||
which the predicate is false. If *predicate* is ``None``, return the items |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
False
is also correct here; this change seems to be pedantic churn only, and has no real value, IMO. I'd keep the current text. The following sentence uses None
; I don't see any reason not to use False
here. I'd consider leaving this as it is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, False
explicitly means the Python object False
, no other false objects. So that's incorrect here. The None
case is different.
Thanks @pochmann for the PR, and @rhettinger for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
GH-102219 is a backport of this pull request to the 3.11 branch. |
…102189) (cherry picked from commit 81bf10e) Co-authored-by: Stefan Pochmann <[email protected]>
(cherry picked from commit 81bf10e) Co-authored-by: Stefan Pochmann <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.