-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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-24618: Add a check in the code constructor. #8283
bpo-24618: Add a check in the code constructor. #8283
Conversation
Check that the size of the varnames tuple is enough at least for all arguments.
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
GH-8291 is a backport of this pull request to the 3.7 branch. |
Check that the size of the varnames tuple is enough at least for all arguments. (cherry picked from commit bd47384) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 2.7. |
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Check that the size of the varnames tuple is enough at least for all arguments.. (cherry picked from commit bd47384) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
GH-8311 is a backport of this pull request to the 3.6 branch. |
Check that the size of the varnames tuple is enough at least for all arguments.
https://bugs.python.org/issue24618