Make tests pass after year 2027

[bmwiedemann]

What do these changes do?

These changes are necessary to allow tests to pass after 2027-05-31

Are there changes in behavior for the user?

No

Is it a substantial burden for the maintainers to support this?

No

Related issue number

NA

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES/ folder

  • name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)

  • if you don't have an issue number, change it to the pull request
    number after creating the PR

    • .bugfix: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    • .misc: Changes that are hard to assign to any of the above
      categories.

  • Make sure to use full sentences with correct case and punctuation,
    for example:

    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.

    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.

Note: I tested that tests pass on i586 and x86_64.

Note2: year 3024 was chosen because it is far enough into the future and it matches the previous day-of-week, so that the diff is more readable. And the previous "Wed, 09 Jun 2030" actually got the day-of-week wrong.

Background:
As part of my work on reproducible builds for openSUSE, I check that software still gives identical build results in the future.
The usual offset is +16 years, because that is how long I expect some software will be used in some places.
This showed up failing tests in our python-aiohttp 3.13.3 package build.
See https://reproducible-builds.org/ for why this matters.

[codspeed-hq]

Merging this PR will not alter performance

✅ 59 untouched benchmarks

---

_{Comparing bmwiedemann:fix2027 (e91eb20) with master (eaeba86)¹}

Footnotes

1. No successful run was found on master (aa2a195) during the generation of this report, so eaeba86 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.77%. Comparing base (eaeba86) to head (e91eb20).
⚠️ Report is 2 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #12088      +/-   ##
==========================================
- Coverage   98.77%   98.77%   -0.01%     
==========================================
  Files         128      128              
  Lines       44890    44890              
  Branches     2383     2383              
==========================================
- Hits        44341    44340       -1     
  Misses        390      390              
- Partials      159      160       +1     

Flag	Coverage Δ
CI-GHA	98.63% <ø> (-0.01%)	⬇️
OS-Linux	98.37% <ø> (ø)
OS-Windows	96.71% <ø> (ø)
OS-macOS	97.61% <ø> (-0.01%)	⬇️
Py-3.10.11	97.16% <ø> (-0.01%)	⬇️
Py-3.10.19	97.64% <ø> (ø)
Py-3.11.14	97.84% <ø> (-0.01%)	⬇️
Py-3.11.9	97.37% <ø> (ø)
Py-3.12.10	97.46% <ø> (-0.01%)	⬇️
Py-3.12.12	97.93% <ø> (ø)
Py-3.13.12	98.18% <ø> (-0.01%)	⬇️
Py-3.14.3	98.14% <ø> (ø)
Py-3.14.3t	97.24% <ø> (-0.01%)	⬇️
Py-pypy3.11.13-7.3.20	97.38% <ø> (-0.01%)	⬇️
VM-macos	97.61% <ø> (-0.01%)	⬇️
VM-ubuntu	98.37% <ø> (ø)
VM-windows	96.71% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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