Test on Python 3.14 release candidate 3

[cclauss]

Test on Python 3.14 release candidate 3

Example

Fixes #[Issue Number]

Description

Briefly describe the changes in this pull request.

• [Summary of major changes]
• [Summary of minor changes]
• [Any other relevant information]

I think this actually works, but I find poetry's messages to be indecipherable.

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.
Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• Test A
• Test B

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented on my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have used Conventional Commits for my commit messages
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots

Attach screenshots or screen recordings of the changes, if any.

Additional Context

Add any other context or information about the pull request here.

[cclauss]

@leycec, your review, please, on the failing test?

[efa2d19]

tests fail w/ beartype errors, maybe the latest minor cause the problems, try w/ the prev one

[cclauss]

I would not have tried to upgrade beartype if it had succeeded but it did not...
https://github.com/mac-cleanup/mac-cleanup-py/actions/runs/17681246199/job/50255735335#step:5:1120

[leycec]

Thanks so much for pinging me onboard, @cclauss. First, allow me to uselessly apologize for @beartype failing you here. Second, allow me to uselessly admit I can't replicate this issue locally on my end. This is a shared tragedy. 2025 do be like that.

The following minimal-length example succeeds for me:

from beartype import beartype
from pathlib import Path

@beartype
def check_exists(path: Path | str, *, expand_user: bool = True) -> bool:
    pass

Notably, the problematic Path | str that appears to be failing for you succeeds for me. I have no deep insights. My emoji cat is crying. 😿

How About This...

@beartype 0.22.0rc0 (i.e., release candidate 0) officially lands this Wednesday. If you wouldn't mind holding back on this PR for just a few days, perhaps we could reconvene on Thursday. At that point, I'll kindly request that you bump your mandatory @beartype requirement in pyproject.toml to resemble:

beartype = ">=0.22.0rc0"

Does this seem like a reasonable action plan? If not, emoji cat cries again. 😿 😹

[cclauss]

@ leycec Thanks for jumping in! https://pypi.org/project/beartype --> v0.22.2 gets us to ✅

Congrats on the beartype v0.22.2 release and getting TideLift backing!!

• https://github.com/beartype/beartype/releases

[leycec]

Aww! Thanks so much for all the kind words. Everyone's so nice at this project. I can't wait to run the newest version of mac-cleanup-py on my wife's now-venerable M1, too... That thing's getting a lil' clunky. Autumn cleaning, your time has come. 😁