Replace zip_tricks with zip_kit #100
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
zip_kit is a friendly fork of zip_tricks under MIT license. It includes new features and bug fixes. Use its header/body generation, and use `write_file` for heuristic storage mode (pick the storage mode which is optimal for the content)
|
@fringd lmk 😉 |
|
busy weekend. glad to hear about the friendly fork and continued development of this lovely work ^_^ I'll cut a new version in a few weeks! |
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.
Since zip_tricks development has been put on hold, replace it with zip_kit. zip_kit is a friendly fork of zip_tricks under MIT license. It includes new features and bug fixes. Use its header/body generation, and use
write_filefor heuristic storage mode (pick the storage mode which is optimal for the content).The new zip_kit also has
Streamer#rollback!which will be done automatically if an exception occurs withinwrite_file. This is not handled yet in zipline because the "how" of the retries is more an end-user concern.Paves the way for addressing #78