Added Implementations of __copy__ and __deepcopy__ to show which objects are allowed to be copied and which not.#50
Merged
birkholz-cubert merged 1 commit intomainfrom Jan 21, 2025
Conversation
…s are allowed to be copied and which not
BenMGeo
approved these changes
Jan 20, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If an object is not allowed to be copied, the
__copy__or__deepcopy__functions is implemented but will raise aTypeErroron execution.Currently only
Measurementhas support for a deep copy operation (out of all the objects that manage a handle)For objects that do not manage a sdk handle, the normal python copy behaviour is enough.