| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Only 3.13 and 3.14 need a fix. So please open a new PR for 3.14 only.
After merging that PR, keep only test in this PR.
Sorry, something went wrong.
|
Hi, is there anything else needed for this PR? All CI checks pass and the CLA is signed. Thanks! |
Sorry, something went wrong.
|
Please open a new PR for the 3.14 branch. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 90 days with no activity. |
Sorry, something went wrong.
…Stack mock_open().__exit__ only misbehaves on 3.13 and 3.14, where it was fixed directly by pythonGH-151829 and backported as pythonGH-151861. Only the regression test belongs on main.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
|
The 3.14 PR requested in review is GH-151829 (merged 2026-06-21) and its 3.13 backport GH-151861 also landed, so the fix is covered. As suggested, I have now reduced this PR to the test only — the Lib/unittest/mock.py change and the NEWS entry are dropped. Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Follow-up to the review: only the regression test is kept on main.
The mock_open.__exit__ bug only affects 3.13 and 3.14. It was fixed on those branches directly — GH-151829 for 3.14 (merged), backported to 3.13 as GH-151861 (merged) — so Lib/unittest/mock.py needs no change on main.
Verified locally on main (00348be) that the new test passes without modifying Lib/unittest/mock.py, i.e. main never exhibited the bug; the test guards against a regression towards the 3.13/3.14 behaviour.
No NEWS entry: there is no user-facing change on main.