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

[Guido van Rossum]

Guido van Rossum  added the comment:

Do what you think is best.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Guido van Rossum]

Change by Guido van Rossum :


--
nosy:  -gvanrossum

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Karthikeyan Singaravelan]

Change by Karthikeyan Singaravelan :


Removed file: 
https://bugs.python.org/file48739/TransactionHistory-79b28f7d5748ad20cb8afb107f00330adbcd6d81.csv

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Karthikeyan Singaravelan]

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[SAKCHAI SUKWISET]

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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Nick Coghlan]

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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Yury Selivanov]

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 object to it. 
 Turns out the message is fine, but different from what we raise on iter(1) etc.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[STINNER Victor]

STINNER Victor added the comment:

IMHO the current message is clear enough.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Guido van Rossum]

Guido van Rossum added the comment:

Did you get multiple complaints about this? The existing error doesn't seem so 
bad.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Yury Selivanov]

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 foo
TypeError: 'async for' requires an object with __aiter__ method, got int


>>> for i in 1: pass
...
Traceback (most recent call last):
  File "", line 1, in 
TypeError: 'int' object is not iterable

--
assignee: yselivanov
components: Interpreter Core
messages: 249689
nosy: gvanrossum, haypo, ncoghlan, yselivanov
priority: normal
severity: normal
status: open
title: better exception message when an unsupported object is passed to `async 
for` (pep 492)
type: enhancement
versions: Python 3.5, Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com