[Python-Dev] Timeout for PEP 550 (original) (raw)

[Python-Dev] Timeout for PEP 550 / Execution Context discussion

Paul Moore p.f.moore at gmail.com
Mon Oct 16 04:26:23 EDT 2017

On 16 October 2017 at 02:33, Yury Selivanov <yselivanov.ml at gmail.com> wrote:

Stage 1. A new execution context PEP to solve the problem *just for async code*. The PEP will target Python 3.7 and completely ignore synchronous generators and asynchronous generators. It will be based on PEP 550 v1 (no chained lookups, immutable mapping or CoW as an optimization) and borrow some good API decisions from PEP 550 v3+ (contextvars module, ContextVar class). The API (and C-API) will be designed to be future proof and ultimately allow transition to the stage 2.

So would decimal contexts stick to using threading.local? If so, presumably they'd still have problems with async. If not, won't you still be stuck with having to define the new semantics they have when used with generators? Or would it be out of scope for the PEP to take a position on what decimal does?

Paul

More information about the Python-Dev mailing list