Message 413187 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	asvetlov
Recipients	asvetlov, rhettinger, serhiy.storchaka, uranusjr, yselivanov
Date	2022-02-13.15:10:57
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
I have a design question. Does `print(await a.hello)` look awkward? I'm not speaking about correction. In asyncio code I have seen before, `await val` means waiting for a future object. `await func()` means async function call. `await obj.attr` looks more like a future waiting but, in fact, it is not. Should we encourage such syntax? I have no strong opinion here and like to hear other devs.

I have a design question.
Does `print(await a.hello)` look awkward?
I'm not speaking about correction.

In asyncio code I have seen before, `await val` means waiting for a future object. `await func()` means async function call.

`await obj.attr` looks more like a future waiting but, in fact, it is not.
Should we encourage such syntax?
I have no strong opinion here and like to hear other devs.

History
Date	User	Action	Args
2022-02-13 15:10:57	asvetlov	set	recipients: + asvetlov, rhettinger, serhiy.storchaka, yselivanov, uranusjr
2022-02-13 15:10:57	asvetlov	set	messageid: <[email protected]>
2022-02-13 15:10:57	asvetlov	link	issue46622 messages
2022-02-13 15:10:57	asvetlov	create