Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

python -m snappy -d raises TypeError: cannot unpack non-iterable function object

Open Beginner friendly
#153 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
cli

Research direction

Start in snappy/__main__.py at the unpacking call on line 79, then compare it with the return behavior of get_decompress_function() in snappy_formats.py. Run the reported python3 -m snappy -d real.snappy reproduction; done when decompression through the CLI succeeds without the TypeError while compression and the library API remain unaffected.

Written by the indexing model from the issue text.

Description

python -m snappy -d file.snappy fails with TypeError: cannot unpack non-iterable function object in 0.7.3.

Steps (Ubuntu, Python 3.14, python-snappy 0.7.3 from pip):

python3 -m snappy -c plain.txt real.snappy
python3 -m snappy -d real.snappy

Result of the second command:

TypeError: cannot unpack non-iterable function object

Cause: in snappy/__main__.py line 79, method, read_chunk = formats.get_decompress_function(args.target_format, args.infile) unpacks two values, but get_decompress_function() in snappy_formats.py returns a single function (return decompress_func / return _DECOMPRESS_METHODS[specified_format]). Compression works. Decompressing with the library API directly (snappy.stream_decompress(src, dst)) works for the same file.

Dominant language
Python
Stars
490
Forks
104
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from intake/python-snappy

All issues in intake/python-snappy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.