-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
bpo-46712: Let generate_global_objects.py Run on Earlier Python Versions #31637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpo-46712: Let generate_global_objects.py Run on Earlier Python Versions #31637
Conversation
Hmm, I'm not able to reproduce that failure locally. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The commit title doesn't match what I see in the PR -- how come all these extra ids were added? Were they somehow lost in the offending PR (GH-31261)? I don't see how.
All the added ids are the ones used in the frozen modules. They should have been added in that PR (from running |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see. Perhaps this wasn't caught because I simplified some things in the freeze_modules.py script. (Or if it looks Kumar did so, it was my idea. :-)
...or it may be something else and I was wrong and Kumar's PR is fine. It isn't clear yet. I'm checking. |
Yeah, I compared an old and the new deepfreeze.c output (on Windows) and while there were some differences but not in lines with |
(Those extra identifiers, like |
Yeah, it was my fault. Some changes where I was using |
Sorry for the noise. |
gh-32218) This effectively reverts the Makefile change in gh-31637. I've added some notes so it is more clear what is going on. We also update the "Check if generated files are up to date" job to run "make regen-deepfreeze" to ensure "make regen-global-objects" catches deepfreeze.c. https://bugs.python.org/issue47146
https://bugs.python.org/issue46712