gh-74772: Adds autospec argument for Mock / MagicMock / AsyncMock#154080
Open
claudiubelu wants to merge 3 commits into
Open
gh-74772: Adds autospec argument for Mock / MagicMock / AsyncMock#154080claudiubelu wants to merge 3 commits into
claudiubelu wants to merge 3 commits into
Conversation
Author
|
A few things to note about this PR:
|
Mock can accept a spec object / class as an argument, making sure
that accessing attributes that do not exist in the spec will cause an
AttributeError to be raised, but there is no guarantee that the spec's
methods signatures are respected in any way. This creates the possibility
to have faulty code with passing unittests and assertions.
Example:
from unittest import mock
class Something(object):
def foo(self, a, b, c, d):
pass
m = mock.Mock(spec=Something)
m.foo()
Adds the autospec argument to NonCallableMock and its mock_add_spec method.
These changes are inherited by Mock, MagicMock, AsyncMock.
Passes the spec's attribute with the same name to the child mock (spec-ing
the child), if the mock's autospec is True.
Sets _mock_check_sig only if the given spec is used via autospec, so that
passing plain spec/spec_set does not change existing signature-checking
behavior.
Adds unit tests to validate the fact that the autospecced method signatures are
enforced.
Signed-off-by: Claudiu Belu <cbelu@cloudbasesolutions.com>
Author
|
An interesting note regarding [1] [2] |
claudiubelu
force-pushed
the
bpo-30587-adds-mock-autospec-arg
branch
from
July 21, 2026 18:59
b187ca9 to
59250bc
Compare
…gaps Fix _get_signature_object to handle functools.partial specs via inspect.signature() directly, instead of going through partial.__call__. This was silently disabling signature checking for any partial function / method spec. Preserve an explicit spec given as a list of attribute names alongside autospec, extending the autospecced attribute set instead of letting autospec override it entirely. This allows whitelisting instance attributes that are only set in __init__, which are invisible to autospec. Add tests for: - autospec combined with wraps (sync and async). - autospec on plain functions, partial functions and partial methods. - a function side_effect on an autospec'd method. - a class's __init__ signature being enforced. - autospec + spec list attribute whitelist combination. - a real @Property descriptor is not eagerly triggered by autospec=, mirroring the existing spec= test. - autospec propagates recursively through a class-level attribute that is itself a spec'd object, enforcing the inner object's signatures too. - reset_mock() does not clear _mock_check_sig. - attach_mock() with a Mock(autospec=...) child preserves both call recording and signature enforcement after reparenting. - magic / dunder methods on a MagicMock(autospec=...): existence is still gated by the spec, and __call__'s signature is enforced (against __init__ when autospeccing a class, against __call__ itself when autospeccing an instance). Signed-off-by: Claudiu Belu <cbelu@cloudbasesolutions.com>
Author
|
/cc @ambv Hello, we talked a bit about |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mock can accept a
specobject / class as an argument, making sure that accessing attributes that do not exist in the spec will cause anAttributeErrorto be raised, but there is no guarantee that the spec's methods signatures are respected in any way. This creates the possibility to have faulty code with passing unittests and assertions.Example:
Adds the
autospecargument toNonCallableMockand itsmock_add_specmethod. These changes are inherited byMock,MagicMock,AsyncMock.Passes the spec's attribute with the same name to the child mock (spec-ing the child), if the mock's
autospecis True.Sets
_mock_check_sigonly if the given spec is used viaautospec, so that passing plainspec/spec_setdoes not change existing signature-checking behavior.Adds unit tests to validate the fact that the autospecced method signatures are enforced.
https://bugs.python.org/issue30587
#74772