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

[UTILS] Improve b2view TUI

Open
#653 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
cli, documentation

Research direction

Start with the b2view project script and its tree, meta, vlmeta, and data views; assess navigation using real-world datasets such as parquet files from Hugging Face. Update doc/getting_started/overview.rst or add tools.rst with supported formats, launch instructions, and a screenshot or ASCII rendering, then link it from the parquet-to-blosc2 docs. Done means b2view is easier to browse and discoverable in the documentation.

Written by the indexing model from the issue text.

Description

documentation enhancement sustain-2026

The b2view command-line TUI (installed as a project script) allows to browse visually inspect a .b2nd or .b2z/.b2d file/dir. It has different views (tree, meta, vlmeta, data), but more love is needed to make it working in a smoother way and/or adding new features.

Also, although b2view has a specific guide at https://blosc.org/python-blosc2/guides/b2view.html, this can be improved by providing a better flow of the text.

Suggested work:

  • Use real-world datasets (e.g. coming from parquet files in Hugging Face), and assess navegability on them. Try to improve visual aspects and browsability in general.
  • Add a screenshot or short ASCII rendering of the TUI output
  • Link it from the parquet-to-blosc2 docs (issue 3 above) since that tool and b2view are often used together
Dominant language
Python
Stars
211
Forks
63
Avg merge
1d 9m
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

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 Blosc/python-blosc2

All issues in Blosc/python-blosc2

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.