Skip to content

Prep for release - #90

Merged
GavinHuttley merged 3 commits into
HuttleyLab:developfrom
GavinHuttley:develop
Oct 9, 2026
Merged

GavinHuttley merged 3 commits into
HuttleyLab:developfrom
GavinHuttley:develop

Conversation

@GavinHuttley

@GavinHuttley GavinHuttley commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator

Summary by Sourcery

Update the project’s supported Python versions and release configuration for Python 3.11 through 3.15, including free-threaded builds.

Enhancements:

  • Raise the minimum supported Python version to 3.11 and add support for Python 3.15 and free-threaded Python builds.
  • Update development and test environments to cover standard and free-threaded Python versions through 3.15.

Build:

  • Regenerate the uv lockfile for the updated Python support and dependency constraints.

CI:

  • Update the development testing matrix to use Python 3.11, 3.14, 3.15, and free-threaded 3.14t and 3.15t across supported operating systems.

Documentation:

  • Update the README to document Python 3.11 or newer support.

@sourcery-ai

sourcery-ai Bot commented Oct 9, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Prepares the project for release by dropping Python 3.10, adopting Python 3.11–3.15 support, and extending nox/CI coverage to free-threaded Python 3.14t and 3.15t runtimes. The lockfile is regenerated, and CI now relies on uv/nox environment provisioning rather than a separate setup-python step.

File-Level Changes

Change Details Files
Raise the supported Python baseline and align static typing with it.
  • Require Python 3.11 or newer for installation.
  • Drop the Python 3.10 classifier and add Python 3.15 and free-threading beta classifiers.
  • Update mypy’s target version to Python 3.11.
pyproject.toml
Expand the nox test matrix to cover current and free-threaded Python runtimes.
  • Test standard Python 3.11–3.15 environments.
  • Add test and coverage sessions for Python 3.14t and 3.15t using uv-backed virtual environments.
noxfile.py
Update CI’s development test matrix for newer standard and free-threaded interpreters.
  • Replace the old 3.10/3.14 matrix with 3.11, 3.14, 3.15, 3.14t, and 3.15t entries across all configured operating systems.
  • Remove the redundant setup-python step, leaving uv/nox to provision environments.
.github/workflows/testing_develop.yml
Regenerate the dependency lockfile for the updated release constraints and environment matrix.
  • Update resolved dependency metadata and package entries to reflect the new Python requirement.
uv.lock

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 2 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="pyproject.toml" line_range="26" />
<code_context>
     "Programming Language :: Python :: 3.13",
     "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: 3.15",
+    "Programming Language :: Python :: Free Threading :: 2 - Beta",
 ]
 dependencies = []
</code_context>
<issue_to_address>
**Concurrent log messages are dropped**

When one thread sets `log_file_path` while another calls `log_message` on the same caching logger, `log_message` can append to `_messages` while the path setter is flushing the list; the setter then replaces it with an empty list, so the concurrent message is never written to the log file.

Synchronize the cache transition in the path setter with appends in `log_message`.
</issue_to_address>

### Comment 2
<location path="pyproject.toml" line_range="13" />
<code_context>
 license-files = ["LICENSE"]
 authors = [{ name = "Gavin Huttley", email = "Gavin.Huttley@anu.edu.au" }]
-requires-python = ">=3.10"
+requires-python = ">=3.11"
 keywords = ["science", "logging"]
 classifiers = [
</code_context>
<issue_to_address>
**Python support badge misleads users**

When a Python 3.10 user relies on the README badge to determine compatibility, the README advertises Python 3.10+ support, but the package metadata rejects Python 3.10 during installation, so the advertised minimum is incorrect.

Update the README badge to advertise Python 3.11+ support.
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread pyproject.toml
"Programming Language :: Python :: 3.13",
"Programming Language :: Python :: 3.14",
"Programming Language :: Python :: 3.15",
"Programming Language :: Python :: Free Threading :: 2 - Beta",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Concurrent log messages are dropped

When one thread sets log_file_path while another calls log_message on the same caching logger, log_message can append to _messages while the path setter is flushing the list; the setter then replaces it with an empty list, so the concurrent message is never written to the log file.

Synchronize the cache transition in the path setter with appends in log_message.

Prompt for AI agents
In `pyproject.toml` at line 26:

**Concurrent log messages are dropped**

When one thread sets `log_file_path` while another calls `log_message` on the same caching logger, `log_message` can append to `_messages` while the path setter is flushing the list; the setter then replaces it with an empty list, so the concurrent message is never written to the log file.

Synchronize the cache transition in the path setter with appends in `log_message`.

Comment thread pyproject.toml
@GavinHuttley
GavinHuttley merged commit fa42284 into HuttleyLab:develop Oct 9, 2026
15 checks passed
@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown

Coverage Report for CI Build 38006931546

Coverage remained the same at 97.051%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 373
Covered Lines: 362
Line Coverage: 97.05%
Coverage Strength: 11.65 hits per line

💛 - Coveralls

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant