Re: [Python-ideas] New PEP 550: Execution Context

Nick, you nailed it with your example. In short: current PEP 550 defines Execution Context in such a way, that generators and iterators will interact differently with it. That means that it won't be possible to refactor an iterator class to a generator and that's not acceptable. I'll be

Re: [Python-ideas] New PEP 550: Execution Context

On Mon, Aug 14, 2017 at 12:56 PM, Guido van Rossum wrote: > Could someone (perhaps in a new thread?) summarize the current proposal, > with some examples of how typical use cases would look? This is an important > topic but the discussion is way too voluminous for me to follow

Re: [Python-ideas] New PEP 550: Execution Context

Yury Selivanov wrote: > This is a new PEP to implement Execution Contexts in Python. It dawns on me that I might be able to use ECs to do a better job of implementing flufl.i18n's translation contexts. I think this is another example of what the PEP's abstract describes as "Context managers

Re: [Python-ideas] New PEP 550: Execution Context

Hi Barry, Yes, i18n is another use-case for execution context, and ec should be a perfect fit for it. Yury ___ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct:

Re: [Python-ideas] New PEP 550: Execution Context

On 14 August 2017 at 02:33, Yury Selivanov wrote: > On Sat, Aug 12, 2017 at 10:09 PM, Nick Coghlan wrote: >> That similarity makes me wonder whether the "isolated or not" >> behaviour could be moved from the object being executed and directly >> into

Re: [Python-ideas] New PEP 550: Execution Context

Could someone (perhaps in a new thread?) summarize the current proposal, with some examples of how typical use cases would look? This is an important topic but the discussion is way too voluminous for me to follow while I'm on vacation with my family, and the PEP spends too many words on