gh-93627: Align copy module behaviour with pickle module#109498
Uh oh!
There was an error while loading. Please reload this page.
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.
In this PR we align the behavior of the
copymodule with thepicklemodule. See #93627 and #103035 for more discussion. For example:The more consistent behaviour in this PR has to be weighted against the alternative option: keep the current behaviour (which is backwards compatible).
Some notes:
Changing the behaviour does not break any existing unit tests. For either this PR, or the keeping the current behaviour, we can add tests to ensure the behaviour in the future.
One variation is to change the behavior of
__reduce_ex__and__reduce__attributes to align withpickle, but do not modify the behaviour of__copy__and__deepcopy__(these methods are specific for the copy module and not present in the pickle module