Capture and serialization of object values #27
Merged
Conversation
This file contains 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
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.
This PR adds functionality to store values of simple object types in the captured provenance.
The built-in Python types
str,bool,int,floatandcomplex, and the NumPy numeric types (e.g.,numpy.float64) are stored by default. The values are stored in RDF using theprov:valueproperty.The user can store the values of additional (more complex) types using the
store_valuessetting via the functionalpaca_setting. This setting accepts a list of strings defining the full Python path to the object. For example, to store values of dictionaries, the list should have the'builtins.dict'entry. In this case, the value is obtained by type casting the object to a string usingstr.