You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
David is correct, most PEPs are historical records of design decisions that cease to be updated once completed. The language reference is the normative guide for current behaviour.
The exception is "informational" and "process" PEPs, which cover things that are not covered in the language reference, as well the occasional Standards Track PEP which ends up not being incorporated into the language reference properly (for example, until the import section was added to the language reference in Python 3.3, PEP-302 was the best available reference documentation).
Activity
msmhrt commentedon Jan 21, 2014
Although PEP-342 says foo(yield 42) is legal, Lib/test/test_grammar.py says:
BTW, It seems that foo(yield 42) written in ECMAScript 6 is OK.
bitdancer commentedon Jan 21, 2014
Most PEPs are historical documents once they are final, so I don't think there is actually anything to fix here. But I could be wrong.
ncoghlan commentedon Jan 25, 2014
David is correct, most PEPs are historical records of design decisions that cease to be updated once completed. The language reference is the normative guide for current behaviour.
The exception is "informational" and "process" PEPs, which cover things that are not covered in the language reference, as well the occasional Standards Track PEP which ends up not being incorporated into the language reference properly (for example, until the import section was added to the language reference in Python 3.3, PEP-302 was the best available reference documentation).