ZipZap
zipfly
Our great sponsors
| ZipZap | zipfly | |
|---|---|---|
| 2 | 11 | |
| 1,217 | 517 | |
| - | 0.2% | |
| 0.0 | 4.0 | |
| over 2 years ago | 7 months ago | |
| Objective-C | Python | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ZipZap
-
Awesome macOS Libraries List
ZipZap - zip file I/O library. Language: Objective-C.
-
Python – Create large ZIP archives without memory inflation
Streaming zip file is going to have issues when compression ratio is not 0 for some implementations (such as ZipFileStream from Java / Android). I fixed this a few years ago for ZipZap: https://github.com/pixelglow/ZipZap/pull/155
Particularly, the local header (per file) is written before the file content, and you cannot get accurate compressed size prior to actual compression. Central file header is at the end of the file, so there is no problem to get accurate compressed size, but some zip reader implementations (such as ZipFileStream) cannot use central file header (because it is at the end), and will use the wrong compressed size.
zipfly
- ZipFly 6.0.5
- GitHub - sandes/zipfly: Writing large ZIP archives without memory inflation
- Python3 – Writing large ZIP archives without memory inflation
- Python – Writing large ZIP archives without memory inflation
-
Help me understand working with streams in Python
If you get that far then you'll have a decent understanding on how zip and io can work. My advice then would be to hop in a time machine and check out https://github.com/BuzonIO/zipfly.
- GitHub - BuzonIO/zipfly: Writing large ZIP archives without memory inflation
- Zipfly - Write large ZIP archives without memory inflation in Python
-
Python – Create large ZIP archives without memory inflation
The code is perplexing. Why do you need to say int('0x1', 16) and int('0x2', 16)? Why not just write 0x1 and 0x2? Or just plain 1 and 2?
I'm also perplexed by the goal as this seems to just call zipfile.write under the hood, which already does what this tries to accomplish?
[0] https://github.com/BuzonIO/zipfly/blob/master/zipfly/zipfly....
What are some alternatives?
ZipArchive - ZipArchive is a simple utility class for zipping and unzipping files on iOS, macOS and tvOS.
python-zipstream - Like Python's ZipFile module, except it works as a generator that provides the file in many small chunks.
Zip Foundation - Effortless ZIP Handling in Swift
stream-unzip - Python function to stream unzip all the files in a ZIP archive on the fly
KZFileWatchers - A micro-framework for observing file changes, both local and remote. Helpful in building developer tools.
zipstream - Simple python library for streaming zip files which are created dynamically, without using any temporary files
FileExplorer - FileExplorer is a powerful iOS file browser that allows its users to choose and remove files and/or directories
zipstreamer - Zip File Streaming Microservice - stream zip files on the fly
AppFolder - 🗂 Never use NSSearchPathForDirectoriesInDomains again
www - Generic www flask server with phinka module
Ares - Zero-setup P2P file transfer between Macs and iOS devices
datasette - An open source multi-tool for exploring and publishing data