Fixed 1714 expose_inputs deepcopy default value#2347
Merged
Conversation
Allowing deepcopy of a stored node to support this use case. See the bug report #1741 for default but simply put if you expose the inputs of a workchain with a stored default plumpy will try to deepcopy that default value which was expecting because of a ban on deepcopying stored nodes.
sphuber
approved these changes
Dec 12, 2018
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
3 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.
Allowing deepcopy of a stored node to support this use case. See the
bug report #1741 for
default but simply put if you expose the inputs of a workchain with a
stored default plumpy will try to deepcopy that default value which was
expecting because of a ban on deepcopying stored nodes.