Author yselivanov
Recipients Jelle Zijlstra, giampaolo.rodola, gvanrossum, ncoghlan, rhettinger, vstinner, yselivanov
Date 2017-03-01.15:37:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488382671.92.0.457324507747.issue29679@psf.upfronthosting.co.za>
In-reply-to
Content
> In formulating my question for the list, it occurred to me that while asynccontextmanager doesn't need to depend on asyncio, the AsyncExitStack proposed in issue 29302 likely will, which pushes me towards favouring the `asyncio.contextlib.asynccontextmanager` approach.

As I said in [1], I think asynccontextmanager and AsyncExitStack should be framework agnostic and thus stay in the top level contextlib package.

IMO AsyncExitStack should not be dependent on asyncio, and if it is it means we would need to tweak its design to make it not to.  I'll take a look at the other issue to see if I can help.

[1] https://mail.python.org/pipermail/python-dev/2017-March/147505.html
History
Date User Action Args
2017-03-01 15:37:51yselivanovsetrecipients: + yselivanov, gvanrossum, rhettinger, ncoghlan, vstinner, giampaolo.rodola, Jelle Zijlstra
2017-03-01 15:37:51yselivanovsetmessageid: <1488382671.92.0.457324507747.issue29679@psf.upfronthosting.co.za>
2017-03-01 15:37:51yselivanovlinkissue29679 messages
2017-03-01 15:37:51yselivanovcreate