GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Pin a libtmux minor series in the README without naming one by tony · Pull Request #824 · tmux-python/libtmux

Conversation

@tony

@tony tony commented Nov 6, 2026

Copy link
Copy Markdown
Member

The README's install tip told projects to pin libtmux==0.50.* (and "0.50.*" in pyproject.toml), while the unreleased series is 0.63, so a reader copying it pinned a release thirteen minors old. The tip now shows how to print the installed version and pins that minor series as 0.N.*, so it stays true across releases. It keeps the reason: a pre-1.0 minor release can change the API.

  • docs(README) Pin a minor series without naming one

Checks: python -c 'import libtmux; print(libtmux.__version__)' prints 0.62.0 in this checkout, and the README no longer contains 0.50. The version numbers in MIGRATION and the deprecation notes in options.py are deliberate history and are unchanged.

Tool use: Claude Code made the change and opened this pull request at the maintainer's request.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@codecov

codecov Bot commented Nov 6, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.45%. Comparing base (03c4c4b) to head (12faf93).

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #824      +/-   ##
==========================================
+ Coverage   52.37%   52.45%   +0.08%     
==========================================
  Files          26       26              
  Lines        3729     3729              
  Branches      747      747              
==========================================
+ Hits         1953     1956       +3     
+ Misses       1472     1469       -3     
  Partials      304      304              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@tony
docs(README) Pin a minor series without naming one
90a8744
why: The install tip told projects to pin libtmux==0.50.*, while the
unreleased series is 0.63, so a reader copying it pinned a release
thirteen minors old. A version number in the README goes stale on every
minor release.

what:
- Show how to print the installed version, and pin its minor series as
  0.N.* in requirements.txt and pyproject.toml
- Say why: a pre-1.0 minor release can change the API
@tony
tony force-pushed the docs-readme-pin-series branch from 99e587f to 90a8744 Compare November 7, 2026 02:20
tony added 2 commits November 6, 2026 20:28
@tony
py(deps[dev]) Raise Ruff floor to 0.17.3
5edd94d
why: Keep development and CI linting on the same Ruff release,
including corrected f-string conversions and safer lint fixes.

what:
- Raise Ruff floors in the development and lint dependency groups
- Lock Ruff 0.17.3 with its published source and wheel hashes

Ruff release notes:
https://github.com/astral-sh/ruff/releases/tag/0.17.2
https://github.com/astral-sh/ruff/releases/tag/0.17.3
@tony
CHANGES(docs): Record the Ruff development floor
12faf93
why: Contributors need the lint-tool requirement alongside other
development environment changes.

what:
- Document the Ruff 0.17.3 minimum for development and lint checks

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@tony
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.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.