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

Move uncovered libs from `libtmux.common` to `libtmux._internal`

Open
#377 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend-api-design

Research direction

Start by reviewing the APIs and libraries currently under libtmux.common, then compare them with the intended role of libtmux._internal. Decide which uncovered APIs should move so it is clear which are excluded from the version policy. Done means the internal boundary is deliberate and production-facing APIs remain clearly identified.

Written by the indexing model from the issue text.

Description

If an API is subject to break lets make it obvious its not covered by version policy

Not sure if all internal APIs will be in _internal but we need to be deliberate about making APIs ship in prod releases

Dominant language
Python
Stars
1.2k
Forks
127
Avg merge
2h 13m
Merged PRs (30d)
1

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 tmux-python/libtmux

All issues in tmux-python/libtmux

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.