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
Clarify that the itertools pure python equivalents are only approximate. #70114
Comments
According to the docs
But it raises a TypeError when used this way:
The |
Huh. I always thought the wording was "roughly equivalent to". This is a consequence of C vs python, and is the reason the docstring uses the [] notation. |
Should 'roughly equivalent to' be added as a note to the docs? |
I'm okay with changing the docs to "roughly equivalent to". That will help prevent the occasional misreading as "precisely equivalent in every respect". |
Issue bpo-25926 |
Attached a diff |
New changeset 613314c3f9ed by Raymond Hettinger in branch '3.5': New changeset e67e970de54a by Raymond Hettinger in branch 'default': |
New changeset f66c30f66235 by Raymond Hettinger in branch '2.7': |
Nofar, thanks for the patch. |
New changeset 35fa2ec1f237 by Serhiy Storchaka in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: