Session serialization to zipped yaml/tsv #149
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
dweindl
force-pushed
the
gh24_yaml
branch
5 times, most recently
from
18b6b93 to
0389e19
Compare
Related to #24. Serialize session data to a zipped yaml file and tsv files instead of pickling, so the data is portable across different versions of Python and other dependencies. Currently, this is still too slow. If we can reduce the amount of data without losing much, this could be become viable.
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.
Serialize session data to a zipped yaml file and tsv files instead of pickling, so the data is portable across different versions of Python and other dependencies.
Added as an optional, more portable, but significantly slower alternative to numpy/pickle.
Closes #24.