| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Do you need to bump the pyc magic number as well? I forgot whether bytecode invalidation matters here. |
Sorry, something went wrong.
|
The changes look correct to me, but I've not looked that closely at the conditional annotation code. |
Sorry, something went wrong.
@JelleZijlstra: Can you update the magic number (in Include/internal/pycore_magic_number.h) please? |
Sorry, something went wrong.
|
Done |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. The changes does fix the crash and the added tests check for non-regression.
Sorry, something went wrong.
|
Thanks @JelleZijlstra for the PR, and @vstinner for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
|
Sorry, @JelleZijlstra and @vstinner, I could not cleanly backport this to 3.14 due to a conflict. cherry_picker 7a6fd4a45deee23b827bf8e32bde172e14921ed6 3.14 |
Sorry, something went wrong.
… listcomp (python#138363) (cherry picked from commit 7a6fd4a)
|
GH-138749 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
|
Merged, thanks @JelleZijlstra. I wrote a backport to 3.14 (I adapted the magic number for 3.14). |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The bug was that we used the wrong name list to get __conditional_annotations__, which caused us to emit a SET_ADD that was adding to something that wasn't a set. This manifested as a hang on debug builds and a crash on release builds for whatever reason, but the issue became more apparent when I added an assertion to setobject.c to make sure we were only adding to sets.