@Pierre-Sassoulas how do you feel about xfailing those 3 failing deque tests on python 3.13? We need to get some sort of hotfix out and I can't commit to debugging them. edit: got it, was just a "haste makes waste" thing!

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.19%. Comparing base (cae4388) to head (94036c3).
Report is 42 commits behind head on main.

@@            Coverage Diff             @@
##             main    #2647      +/-   ##
==========================================
- Coverage   93.20%   93.19%   -0.01%     
==========================================
  Files          93       93              
  Lines       11077    11078       +1     
==========================================
  Hits        10324    10324              
- Misses        753      754       +1     

The backport to maintenance/3.3.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-maintenance/3.3.x maintenance/3.3.x
# Navigate to the new working tree
cd .worktrees/backport-maintenance/3.3.x
# Create a new branch
git switch --create backport-2647-to-maintenance/3.3.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 fe01bda8d9b3e118b1713f726dea6efffa0c6b07
# Push it to GitHub
git push --set-upstream origin backport-2647-to-maintenance/3.3.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-maintenance/3.3.x

Then, create a pull request where the base branch is maintenance/3.3.x and the compare/head branch is backport-2647-to-maintenance/3.3.x.

@Pierre-Sassoulas Well, now I'm doubtful this accomplished anything because I'm having trouble reproducing the original issue. Ugh. I have no idea how to proceed.

Should we create a brain for collection.abc when the python interpreter is > 3.13.1 ? Feels dirty but we might not have a choice.

Well that's what I tried, but it didn't make a difference. At a loss until I can repro the problem.

okay, progress.

verified everything still fails with 3.13.6 (not a big deal, haven't updated pylint yet)

but pylint job passes with this commit adding a brain for the underlying _collections_abc.

never mind, that job was running python 3.12 for some reason. back to square one.