[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Guido van Rossum added the comment: Do what you think is best. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Change by Karthikeyan Singaravelan : Removed file: https://bugs.python.org/file48739/TransactionHistory-79b28f7d5748ad20cb8afb107f00330adbcd6d81.csv ___ Python tracker ___

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Change by Karthikeyan Singaravelan : -- components: -2to3 (2.x to 3.x conversion tool) type: resource usage -> enhancement versions: -Python 2.7, Python 3.5, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Change by SAKCHAI SUKWISET : -- components: +2to3 (2.x to 3.x conversion tool) type: enhancement -> resource usage versions: +Python 2.7, Python 3.7, Python 3.8, Python 3.9 Added file: https://bugs.python.org/file48739/TransactionHistory-79b28f7d5748ad20cb8afb107f00330adbcd6d81.csv

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Nick Coghlan added the comment: In tandem with an "asynchronous iterable" glossary entry, that could be a nice improvement. Even without such a change the first hit for "python asynchronous iterable" is PEP 492, so it will get folks pointed in the right direction. --

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

New submission from Yury Selivanov: Should we raise something like "'int' object is not an asynchronous iterable", instead of "'async for' requires an object with __aiter__ method, got int"? >>> foo().send(None) Traceback (most recent call last): File "", line 1, in File "", line 2, in

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

STINNER Victor added the comment: IMHO the current message is clear enough. -- ___ Python tracker ___ ___

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Yury Selivanov added the comment: I saw this reddit thread: https://www.reddit.com/r/Python/comments/3ewnwq/async_function_as_generator_for_async_for/ where people are struggling with understanding how 'async for' works. Which led me to check what error messages we raise when we pass a wrong

[issue24995] better exception message when an unsupported object is passed to `async for` (pep 492)

Guido van Rossum added the comment: Did you get multiple complaints about this? The existing error doesn't seem so bad. -- ___ Python tracker ___