Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make tests pass after year 2039 (#7191)
<!-- Thank you for your contribution! --> ## What do these changes do? Make tests pass after year 2039 ## Are there changes in behavior for the user? none ## Related issue number N/A 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` package build. See https://reproducible-builds.org/ for why this matters. ## Checklist - [X] I think the code is well written - [X] 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. - [x] Add a new news fragment into the `CHANGES` folder * name it `<issue_id>.<type>` for example (588.bugfix) * if you don't have an `issue_id` change it to the pr id after creating the pr * ensure type is one of the following: * `.feature`: Signifying a new feature. * `.bugfix`: Signifying a bug fix. * `.doc`: Signifying a documentation improvement. * `.removal`: Signifying a deprecation or removal of public API. * `.misc`: A ticket has been closed, but it is not of interest to users. * Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."
- Loading branch information