-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
bpo-29607: Fix stack_effect computation for CALL_FUNCTION_EX #202
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-29607: Fix stack_effect computation for CALL_FUNCTION_EX #202
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow these steps to rectify the issue:
Thanks again to your contribution and we look forward to looking at it! |
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.
Could you add an entry to Misc/NEWS
?
It might be like this:
Core and Builtins
-----------------
- bpo-29607: Fix stack effect computation for CALL_FUNCTION_EX opcode.
Misc/NEWS
Outdated
@@ -10,6 +10,8 @@ What's New in Python 3.7.0 alpha 1? | |||
Core and Builtins | |||
----------------- | |||
|
|||
- bpo-29607: Fix stack_effect computation for CALL_FUNCTION_EX |
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.
Please add "Patch by <yourname>
."
Misc/NEWS
Outdated
@@ -10,6 +10,9 @@ What's New in Python 3.7.0 alpha 1? | |||
Core and Builtins | |||
----------------- | |||
|
|||
- bpo-29607: Fix stack_effect computation for CALL_FUNCTION_EX. | |||
Patch by Matthieu Dartiailh |
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.
Add a period at the end of the entry.
) (cherry picked from commit 3a9ac82)
@MatthieuDartiailh I'm sorry, but I missed "CLA not signed" label. |
It is waiting to be reviewed. |
I think signing CLA is not required for such trivial change. Since the bug was reported anyone could write the patch. But if Matthieu wants to continue his contributing, signing CLA is required. |
Now that we have C99 designated initializers, we don't need the STACKLESS_DECLARE_METHOD magic any longer. Replacing it with explicit initializers has several advantages: - faster startup time - less magic, code is simpler to reason about - no memory leak - no initialization race for sub-types between init_stackless_methods() and PyType_Ready().
Now that we have C99 designated initializers, we don't need the STACKLESS_DECLARE_METHOD magic any longer. Replacing it with explicit initializers has several advantages: - faster startup time - less magic, code is simpler to reason about - no memory leak - no initialization race for sub-types between init_stackless_methods() and PyType_Ready().
Signed-off-by: Pablo Galindo <[email protected]> Signed-off-by: Pablo Galindo <[email protected]>
No description provided.