Skip to content
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

gh-118767: Make bool(NotImplemented) raise TypeError #118775

Merged
merged 5 commits into from
May 8, 2024

Conversation

JelleZijlstra
Copy link
Member

@JelleZijlstra JelleZijlstra commented May 8, 2024

>>> bool(NotImplemented)
Traceback (most recent call last):
  File "<python-input-0>", line 1, in <module>
    bool(NotImplemented)
    ~~~~^^^^^^^^^^^^^^^^
TypeError: NotImplemented should not be used in a boolean context

📚 Documentation preview 📚: https://cpython-previews--118775.org.readthedocs.build/

@JelleZijlstra JelleZijlstra merged commit 3c079a0 into python:main May 8, 2024
38 checks passed
@JelleZijlstra JelleZijlstra deleted the boolnotimp branch May 8, 2024 18:12
@@ -57,6 +57,9 @@ A small number of constants live in the built-in namespace. They are:
it currently evaluates as true, it will emit a :exc:`DeprecationWarning`.
It will raise a :exc:`TypeError` in a future version of Python.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed. And maybe the whole text of the note can be reworded.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I'll submit another PR addressing your comments.

@@ -174,6 +174,9 @@ for more details.
it currently evaluates as true, it will emit a :exc:`DeprecationWarning`.
It will raise a :exc:`TypeError` in a future version of Python.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed.

# a TypeError).
self.assertWarns(DeprecationWarning, bool, NotImplemented)
with self.assertWarns(DeprecationWarning):
self.assertRaises(TypeError, bool, NotImplemented)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test should be renamed.

self.assertWarns(DeprecationWarning, bool, NotImplemented)
with self.assertWarns(DeprecationWarning):
self.assertRaises(TypeError, bool, NotImplemented)
with self.assertRaises(TypeError):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TypeError is raised when you just call a function with wrong number of arguments, for example:

with self.assertRaises(TypeError):
    self.assertEqual(NotImplemented)

It is better to not use assertTrue() (which does not work here), but directly test the boolean value:

if NotImplemented:
    pass

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll also change it to use assertRaisesRegex to test that we're getting the expected TypeError and not some other one.

@@ -0,0 +1,2 @@
Using :data:`NotImplemented` in a boolean context now raises
:exc:`TypeError`. Contributed by Jelle Zijlstra in :gh:`118767`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't the link to the issue already included in the changelog?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fixed in the new PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants