> Does someone know if with the introduction of the new
optimizations/quickening the PREDICT will still be used in 3.11? If there
are 2 interpretation modes now, the PREDICT probably makes it hard to have
both do the same things since the eval loop doesn't really match what the
bytecode says due
I agree with what Batuhan said. Adding on, I'm very concerned about the
potential maintenance burden for Python implementations.
Just for typing in CPython, some combination of the following knowledge is
required to contribute code:
1. Metaclasses
2. Descriptors and CPython dunders
3. C
@Lrupert
> - Add coverage to X (tens of them, as separate PRs)
I think I know the PRs you're referring to. For the record, some of the PRs
tested hairy code paths in the module I maintain. I would have less confidence
backporting bugfixes touching that code if we didn't have those tests (the
Hi Phillip, thanks for your interest in CPython.
How Python views your code isn't how you view your code. CPython views source
code instead as something called "bytecode/wordcode". This bytecode is a
lower-level intermediary language that the CPython interpreter executes. You
can read more
I've created a new PEP to repeal PEP 509. Please post comments to the Discourse
thread. Thank you!
Discourse thread:
https://discuss.python.org/t/pep-699-remove-private-dict-version-field-added-in-pep-509/19724
Link to the PEP: https://github.com/python/peps/blob/main/pep-0699.rst
