- Notifications
You must be signed in to change notification settings - Fork208
remove mutable default argument in prototype __deepcopy__ method#9
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Contributor
neochief commentedJan 12, 2022
Thanks a lot! |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading.Please reload this page.
We should not use mutable objects as default arguments in python functions/methods, so I fixed it in the prototype class.
Before the change:
Every time we called the
__deepcopy__method (actually called by python when you use copy.deepcopy) without the memo argument, the same dict instance was being used. This happens because default arguments are instantiated atload-module time. Leads to dangerous behaviour: if you update the dict in some method-call, you will use the same updated dict in another calls.Now:
The memo dict is created in every call without the memo argument.
ps: no changes to Output.txt are required