Repository navigation
Conversation
why: Library users need imports in their active Python environment. what: - Replace application-only installation routes with pip and uv - Show valid PEP 621 dependencies and tested-series bounds - Keep development installation in the quickstart
why: Repository fixtures hid prerequisites and cleanup ownership. what: - Add a fixture-free README example on a temporary socket - Explain requested fixtures and downstream doctest setup - Bound server context cleanup to resources the caller owns
why: Echoed command text could falsely signal completed work. what: - Match complete marker lines on fresh output lines - Use monotonic bounds and predicate waits in examples - Distinguish progress, completion and process exit status
why: Examples need to match tmux defaults and shell boundaries. what: - Document explicit split attachment and the default prefix - Qualify history suppression and literal key handling
why: Duplicated guides drifted from the project's actual contracts. what: - Link the authoritative release and changelog policies - Describe configured CI targets and current deprecations - Correct the API landing-page link
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #797 +/- ##
==========================================
- Coverage 52.45% 52.37% -0.09%
==========================================
Files 26 26
Lines 3729 3729
Branches 747 747
==========================================
- Hits 1956 1953 -3
- Misses 1469 1472 +3
Partials 304 304 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Install libtmux into the Python environment that imports it, and use a complete first-use example whose server and temporary socket are cleaned up together. Terminal recipes wait for complete printed marker lines, use monotonic deadlines, and explain the limits of completion markers.
The quickstart and reference pages describe fixture injection, split defaults, shell history, literal keys, active deprecations and configured CI targets. Release guidance links the canonical contributor policies. Existing navigation and historical release entries are preserved.
Validation:
Two existing concerns remain deferred: the skipped shell-prompt capture illustration in the README, and the legacy docs requirements include whose external consumers are unknown.