There's a minor technicality here that might worth clarification.

importsysframe1= [sys._getframe()forain [0]][0]frame2=sys._getframe()assertframe1isframe2local1= [sys._getframe().f_localsforain [0]][0]local2=sys._getframe().f_localsassertlocal1!=local2

Whetherf_locals is a proxy or a dict technically does not entirely depend on theframe. It depends on when is theframe.f_locals call made - inside a comprehension or not.

As you can tell from the example above, theframe is exactly the same frame object, but thef_locals is different.

There's a minor technicality here that might worth clarification. [...]

That's very subtle. Is it explained in PEP 667? I'm not sure how to work this in the existing (pretty sparse) docs forf_locals.

Actually the final behavior we agreed on is slightly different from what PEP 667 proposed. PEP 667 also did not mention howf_locals should work with inline comprehensions. Can we modify PEP 667 after it was accepted? I don't know if we should dump all the details in thef_locals docs because it would be rare for the users to usef_locals inside the comprehension so no need to confuse them, but it would be nice to explain it well in PEP 667.

Actually the final behavior we agreed on is slightly different from what PEP 667 proposed. PEP 667 also did not mention howf_locals should work with inline comprehensions. Can we modify PEP 667 after it was accepted? I don't know if we should dump all the details in thef_locals docs because it would be rare for the users to usef_locals inside the comprehension so no need to confuse them, but it would be nice to explain it well in PEP 667.

Assuming this is about clarifying something that the original text of the PEP did not specify precisely enough, and given that the PEP is brand new, I think it's okay to clarify in the PEP. Although in general PEPs are nowadays seen as historic documents, not as living specifications.

It's not something that has to be done in this PR, but if we think that there are some subtleties here that warrant detailed explanation and that the datamodel docs aren't the right place to do that, one option would be to add a howto similar to the one Larry added in 3.10 to explain the semantics of the__annotations__ attribute:https://docs.python.org/3/howto/annotations.html

It wouldn't really be a howto in the Diataxis sense of the term, but we don't really have a better place for that kind of in-depth article in the CPython docs currently, and there are lots of other articles in that directory that also don't meet Diataxis's strict definition of a "howto" article. And as@gvanrossum says, all the relevant information regarding the semantics here should ideally be findable in the CPython docs somewhere, without having to refer to the PEP, which is a historical document now that it has been accepted.

(But we can probably update the PEP as well, given that it'sonly just been accepted :-)

@AlexWaygood@gaogaotiantian Are you two okay with me merging this? I'm all for iterating later, but I feel it's important to mention at least this much in the beta 1 docs, which I expect will reach a relatively big audience of people who are thinking of testing the beta.

Yes this feels okay for beta.