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
{{ message }}
Repository navigation
Over-aggressive optimization for _GUARD_CODE_VERSION #146018
The optimizer is replacing _GUARD_CODE_VERSION with a watcher, which would be fine if the code object were known.
However, the code object is just the one observed during tracing. The one observed during execution could be different, which is why the guard was added in the first place.
We should only remove the guard if the code version is known.
Correct optimizations would be:
Only remove the first guard (and add the code watcher)
If the function is known and its version is known, remove the guard.
Activity
gh-146018: Disable over-aggressive optimization for _GUARD_CODE_VERSI…
pythongh-146018: Disable over-aggressive optimization for _GUARD_CODE…