`autospec` doesn't work with lazy-imported symbols

Bug report

Bug description:

unittest.mock.patch(target, autospec=True) reads unresolved lazy-import bindings directly from target.__dict__ and autospecs the LazyImportType proxy instead of the imported symbol.

from unittest.mock import patch

lazy from json import dumps

with patch("__main__.dumps", autospec=True) as mock_dumps:
    mock_dumps({})

On CPython main (9d231cbc937f as of now), this raises:

TypeError: 'NonCallableMagicMock' object is not callable

Resolving dumps before patching works. This also affects patch.object, spec=True, and spec_set=True.

A practical example is concurrent.futures.ThreadPoolExecutor, which now uses an explicit lazy import: existing tests such as this one patch it with autospec=True and encounter the same issue.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux, macOS, Windows

Linked PRs

• gh-153977
• gh-157768

从 unittest.mock.patch 和 patch.object 入口开始，并使用 json.dumps 的延迟导入重现该示例。比较 autospec=True 与 spec=True 和 spec_set=True，包括报告中链接的 ThreadPoolExecutor 测试用例；当这些用例能够处理导入的符号且不再出现报告中的 NonCallableMagicMock 错误时，即视为完成。