Repository navigation
Fix decompression CLI format detection - #154
Conversation
|
We seem to need to update the CI workflows - would you like to handle this? |
|
Yes, happy to handle the CI workflow updates. I’ll take a look at the failing workflow and update it as part of this PR. |
|
Yes, I believe they address the same CLI issue. I've already fixed the decompression CLI bug in #154, added regression tests, and pushed an additional fix for the failing sdist CI workflow. Could you please take a look at #154? It includes both the CLI fix and the CI workflow correction. Happy to make any further changes if needed. |
|
The CI runs may not be starting because they need old versions of the OS. |
|
Hi, did you get a chance to look at the PR? |
|
Hi Martin, thanks for reviewing and merging my PR! I've really enjoyed contributing to python-snappy and would love to get more involved in open source. If there are any opportunities for paid contributions, ongoing project work, or relevant roles across your projects, I'd be very interested. Happy to help wherever I can add value! |
|
There is plenty of work to be done in the fsspec family of repositories, if you are interested. I don't have any funding or positions of my own, I can only suggest you look around for contracts which include some fraction of paid OSS time. They are not that common... |
Problem
python -m snappy -draises:TypeError: cannot unpack non-iterable function object
This happens because
get_decompress_function()now returns a single decompression function, while the CLI still tries to unpack it intomethodandread_chunk.Fix
Update the CLI to use the current single-value return API and remove the obsolete
start_chunkargument.Tests
get_decompress_function()python -m snappy -d