Skip to content

bpo-30969: Fix docs about the comparison in absence of __contains__ #2761

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

Merged
merged 4 commits into from
May 30, 2019

Conversation

ztane
Copy link
Contributor

@ztane ztane commented Jul 19, 2017

The documentation doesn't match the implementation, which clearly does x is y or x == y to check if x is the element y from a container. Both the __iter__ and the index-iteration method test the elements using is first. While the document says that x is x means that x == x should be true, it is not true for example in the case of nan:

>>> x == x
False
>>> x is x
True```

The following demonstrates the behaviour that is against the documented behaviour:

```>>> class Foo:
...     def __iter__(self):
...         return iter([x])
... 
>>> x in Foo()
True
>>> any(x == i for i in Foo())
False
>>> class Bar:
...     def __getitem__(self):
...         return [x].__getitem__(self)
... 
>>> class Bar:
...     def __getitem__(self, i):
...         return [x].__getitem__(i)
... 
>>> x in Bar
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: argument of type 'type' is not iterable
>>> x in Bar()
True
>>> any(x == i for i in Bar())
False```

<!-- issue-number: [bpo-30969](https://bugs.python.org/issue30969) -->
https://bugs.python.org/issue30969
<!-- /issue-number -->

Both the `__iter__` and the index-iteration method test the `is` first. While the document says that `x is x` means that `x == x` should be true, it is not true for example in the case of `nan`. 

```>>> x = float('nan') 
>>> x == x
False
>>> x is x
True
>>> class Foo:
...     def __iter__(self):
...         return iter([x])
... 
>>> x in Foo()
True
>>> any(x == i for i in Foo())
False
>>> class Bar:
...     def __getitem__(self):
...         return [x].__getitem__(self)
... 
>>> class Bar:
...     def __getitem__(self, i):
...         return [x].__getitem__(i)
... 
>>> x in Bar
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: argument of type 'type' is not iterable
>>> x in Bar()
True
>>> any(x == i for i in Bar())
False```
@mention-bot
Copy link

@ztane, thanks for your PR! By analyzing the history of the files in this pull request, we identified @birkenfeld, @vadmium and @benjaminp to be potential reviewers.

@serhiy-storchaka serhiy-storchaka added the docs Documentation in the Doc dir label Dec 8, 2018
:meth:`__iter__`, ``x in y`` is ``True`` if some value ``z`` with ``x == z`` is
produced while iterating over ``y``. If an exception is raised during the
iteration, it is as if :keyword:`in` raised that exception.
:meth:`__iter__`, ``x in y`` is ``True`` if some value ``z``, for which the
Copy link
Member

@tirkarthi tirkarthi Jan 8, 2019

Choose a reason for hiding this comment

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

@ztane trailing space in the three lines are causing CI failure. Removing them will fix the issue. Thanks for the patch.

Doc git:(pr_2761) python3 tools/rstlint.py -i tools -i ./venv -i README.rst
[1] reference/expressions.rst:1446: trailing whitespace
[1] reference/expressions.rst:1447: trailing whitespace
[1] reference/expressions.rst:1448: trailing whitespace
3 problems with severity 1 found.

@csabella
Copy link
Contributor

@ztane, please apply the suggestions from @tirkarthi to fix the CI failures. Thanks!

@miss-islington
Copy link
Contributor

Thanks @ztane for the PR, and @csabella for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request May 30, 2019
@bedevere-bot
Copy link

GH-13684 is a backport of this pull request to the 3.7 branch.

miss-islington added a commit that referenced this pull request May 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants