Drop python 3.9 references and move to pytest 9.0.0

[dbasunag]

Summary by CodeRabbit

• Chores
  • Updated minimum Python requirement to 3.10.
  • Upgraded test framework versions (pytest and pytest-cov).
  • Lowered test coverage failure threshold.
  • Adjusted test environment matrix for CI tooling.

[coderabbitai]

Walkthrough

Bumps minimum Python to >=3.10, updates test deps (pytest -> >=9.0.0,<10, pytest-cov -> >=7.0.0,<8), lowers coverage fail threshold (68 -> 60), and removes Python 3.9 from the tox test matrix.

Changes

Cohort / File(s)	Summary
Project metadata & test deps pyproject.toml	Bumped Python requirement to >=3.10; updated pytest and pytest-cov version bounds; reduced coverage fail threshold from 68 to 60.
Test matrix configuration tox.ini	Removed Python 3.9 from envlist; adjusted envlist entries to include only supported Python versions (3.10+).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Check other tooling/config files (CI configs, Dockerfiles) for Python version assumptions.
• Verify test matrix in tox.ini aligns with actual supported interpreters in CI.

Possibly related PRs

• Set supported python version to >=3.9 #119 — earlier change to Python version requirement; relates to version bump progression.
• pyproject.py - set python version to >=3.9 #188 — another prior adjustment to Python version constraint relevant to this bump.

Suggested labels

can-be-merged

Suggested reviewers

• myakove
• rnetser

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main changes: dropping Python 3.9 references and updating pytest to version 9.0.0, which are the primary objectives documented in both pyproject.toml and tox.ini updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update_python

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 979e5ca and 86dde3f.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• pyproject.toml (3 hunks)
• tox.ini (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tox.ini

🔇 Additional comments (3)

pyproject.toml (3)

5-5: Breaking change: Python 3.10 becomes the minimum supported version.

This raises the minimum from 3.9 to 3.10 and aligns with the PR objective. Ensure this breaking change is communicated in release notes or migration guidance if needed.

---

43-43: Clarify the rationale for lowering the coverage threshold by 8 percentage points.

The fail_under threshold has been reduced from 68 to 60, which is a significant relaxation. Please clarify whether this is intentional (e.g., a policy change) or if test coverage has regressed, and provide context for this decision.

---

85-86: Verify test compatibility with pytest 9.0.0 and pytest-cov 7.0.0.

The test dependencies are being bumped to major versions (pytest 8→9, pytest-cov 6→7). Ensure all existing tests pass without modification and that no deprecated pytest features are in use. If the PR includes test updates for compatibility, verify they are comprehensive.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[redhat-qe-bot1]

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

• Reviewer Assignment: Reviewers are automatically assigned based on the "
  "OWNERS file in the repository root
  "
  "* Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are "
  "automatically applied based on changes
  "
  f"* Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
  "
  "* Pre-commit Checks: pre-commit runs "
  "automatically if .pre-commit-config.yaml exists
  "
• Branch Labeling: Branch-specific labels are applied to track the target branch
• Auto-verification: Auto-verified users have their PRs automatically marked as verified

📋 Available Commands

PR Status Management

• /wip - Mark PR as work in progress (adds WIP: prefix to title)
• /wip cancel - Remove work in progress status
• /hold - Block PR merging (approvers only)
• /hold cancel - Unblock PR merging
• /verified - Mark PR as verified
• /verified cancel - Remove verification status
• /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)

Review & Approval

• /lgtm - Approve changes (looks good to me)
• /approve - Approve PR (approvers only)
• /automerge - Enable automatic merging when all requirements are met (maintainers and approvers only)
• /assign-reviewers - Assign reviewers based on OWNERS file
• /assign-reviewer @username - Assign specific reviewer
• /check-can-merge - Check if PR meets merge requirements

Testing & Validation

• /retest tox - Run Python test suite with tox
• /retest python-module-install - Test Python package installation
• /retest all - Run all available tests

Container Operations

• /build-and-push-container - Build and push container image (tagged with PR number)
  • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

• /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
  • Multiple branches: /cherry-pick branch1 branch2 branch3

Label Management

• /<label-name> - Add a label to the PR
• /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

1. Approval: /approve from at least one approver
2. LGTM Count: Minimum 0 /lgtm from reviewers
3. Status Checks: All required status checks must pass
4. No Blockers: No WIP, hold, or conflict labels
5. Verified: PR must be marked as verified (if verification is enabled)

📊 Review Process

Approvers and Reviewers

Approvers:

• dbasunag
• myakove
• rnetser

Reviewers:

• dbasunag
• myakove
• rnetser

Available Labels

• hold
• verified
• wip
• lgtm
• approve
• automerge

💡 Tips

• WIP Status: Use /wip when your PR is not ready for review
• Verification: The verified label is automatically removed on each new commit
• Cherry-picking: Cherry-pick labels are processed when the PR is merged
• Container Builds: Container images are automatically tagged with the PR number
• Permission Levels: Some commands require approver permissions
• Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

[dbasunag]

/lgtm
/approve

[dbasunag]

/verified