News for hackers. Stuff that matters.
Re:Python 3.11 beta vs. 3.10 benchmark by kmod on Wednesday May 18, 2022 @09:27AM (#31422498)
Bit of context for this:

- Cheaper Python frames are enabled by making some semantic changes to the language, mostly by removing some dynamic functionality that no one uses

- "Inlined Python function calls" is a bit misleading: Python functions are not inlined, it's the "code that does the bookkeeping for calling a Python function" that is now eliminated for Python-to-Python calls.

- The most important part of the specializing interpreter is the attribute caching, which is quite significant

Source: I work on Pyston, where we do many similar things (but can't make semantic changes to the language)

Re:Python 3.11 beta vs. 3.10 benchmark by masklinn on Wednesday May 18, 2022 @12:53PM (#31424985)
> - Cheaper Python frames are enabled by making some semantic changes to the language, mostly by removing some dynamic functionality that no one uses

What dynamic functionalities does no one use?

Re:Python 3.11 beta vs. 3.10 benchmark by oblvious-earth on Wednesday May 18, 2022 @07:07PM (#31428737)
Not sure what OP meant but basically internal frame struct has been significantly simplified to contain only essential information required at runtime.

If a user is wanting to get or manipulate debugging information then the old frame struct will be generated when this is called.

Re:Python 3.11 beta vs. 3.10 benchmark by dklend122 on Wednesday May 18, 2022 @11:30AM (#31424013)
What are the goals and positioning of pyston given these other efforts?