| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Summary: On yesterday imports we hit some issues with one of the opcodes we've duplicated. We duplicated it so that we could support optimized python -> python calls when we have our eval hook in place. I landed python/cpython#143532 yesterday which makes it possible for us to just redefine the `IS_PEP523_HOOKED` macro. This macro conveniently already defined in our copy of `ceval_macros.h` so the upgrade to consume this is just deleting our overloaded opcodes and picking up the base ones. Reviewed By: jbower-fb Differential Revision: D90279669 fbshipit-source-id: ecc4d87981554aa5a5bf9f27519622cf17cfe2ed
Use macro to check if PEP 523 is hooked
Use macro to check if PEP 523 is hooked
| Back | FazBrowse Home | New Git URL |
This just moves the checks to see if PEP-523 is replaced to a common macro in the interpreter loop.
This will allow PEP 523 users who re-generate the interpreter loop (as in #142911) to redefine the macro to support their replacement with the optimizer as well if they so choose. And it makes it more explicit what these checks are doing when they're randomly sprinkled around.