GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||
GeezerVison is showing github.com — gh-95795: Move types.next_version_tag to PyInterpreterState by ericsnowcurrently · Pull Request #102343 · python/cpython Conversation
|
| the same __name__, for any __name__. Since that's a static property, it is | ||
| appropriate to declare fixed-size arrays for this. */ | ||
| #define MAX_EQUIV 10 | ||
| #define _Py_TYPE_BASE_VERSION_TAG (2<<16) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Did you mean (1<<16) here? This is currently the same as (1<<17)...
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
FYI, this PR is blocked by code objects being shared for deep-frozen modules. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
It seems like this PR will effectively mean that there will now be only 2^16 type versions available to heap types? This seems too low, since we estimate (for instance) that Instagram likely has somewhere around 2^16 heap types, period, without even considering modifications to types. It seems preferable if we can allocate fewer bits to the static types (since there aren't that many) and more to the heap types. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ignore my above comment; I misunderstood how this PR works. There are still (2^32) - (2^16) types available to heap types, which is much more than plenty. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
* main: pythongh-103801: Tools/wasm linting and formatting (python#103796) pythongh-103673: Add missing ForkingUnixStreamServer and ForkingUnixDatagramServer socketservers (python#103674) pythongh-95795: Move types.next_version_tag to PyInterpreterState (pythongh-102343)
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.