-
Notifications
You must be signed in to change notification settings - Fork 105
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: testing-cabal/mock
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4.0.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: testing-cabal/mock
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 4.0.3
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 8 files changed
- 6 contributors
Commits on Mar 14, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 27d6349 - Browse repository at this point
Copy the full SHA 27d6349View commit details
Commits on Jun 3, 2020
-
Configuration menu - View commit details
-
Copy full SHA for a7002f3 - Browse repository at this point
Copy the full SHA a7002f3View commit details
Commits on Dec 10, 2020
-
bpo-40126: Fix reverting multiple patches in unittest.mock. (GH-19351)
Patcher's __exit__() is now never called if its __enter__() is failed. Returning true from __exit__() silences now the exception. Backports: 4b222c9491d1700e9bdd98e6889b8d0ea1c7321e Signed-off-by: Chris Withers <chris@simplistix.co.uk>
Configuration menu - View commit details
-
Copy full SHA for 902eea1 - Browse repository at this point
Copy the full SHA 902eea1View commit details -
bpo-39966: Revert "bpo-25597: Ensure wraps' return value is used for …
…magic methods in MagicMock" (GH-19734) * Revert "bpo-25597: Ensure wraps' return value is used for magic methods in MagicMock (#16029)" This reverts commit 72b1004657e60c900e4cd031b2635b587f4b280e. Backports: 521c8d6806adf0305c158d280ec00cca48e8ab22 Signed-off-by: Chris Withers <chris@simplistix.co.uk>
Configuration menu - View commit details
-
Copy full SHA for c627515 - Browse repository at this point
Copy the full SHA c627515View commit details -
bpo-41877 Check for asert, aseert, assrt in mocks (GH-23165)
Currently, a Mock object which is not unsafe will raise an AttributeError if an attribute with the prefix assert or assret is accessed on it. This protects against misspellings of real assert method calls, which lead to tests passing silently even if the tested code does not satisfy the intended assertion. Recently a check was done in a large code base (Google) and three more frequent ways of misspelling assert were found causing harm: asert, aseert, assrt. These are now added to the existing check. Backports: 4662fa9bfe4a849fe87bfb321d8ef0956c89a772 Signed-off-by: Chris Withers <chris@simplistix.co.uk>
Configuration menu - View commit details
-
Copy full SHA for e5d7551 - Browse repository at this point
Copy the full SHA e5d7551View commit details -
bpo-42532: Check if NonCallableMock's spec_arg is not None instead of…
… call its __bool__ function (GH23613) Check if NonCallableMock's spec_arg is not None instead of call its __bool__ function Backports: c598a04dd29b89ad072245ddaf738badcfb41ac7 Signed-off-by: Chris Withers <chris@simplistix.co.uk>
Configuration menu - View commit details
-
Copy full SHA for f7e3ea8 - Browse repository at this point
Copy the full SHA f7e3ea8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 841c331 - Browse repository at this point
Copy the full SHA 841c331View commit details -
Configuration menu - View commit details
-
Copy full SHA for 93cf533 - Browse repository at this point
Copy the full SHA 93cf533View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 4.0.2...4.0.3