René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Autospeccing with `unittest.mock` is less robust with PEP 649","articleBody":"# Bug report\n\n### Bug description:\n\n```python\nfrom typing import TYPE_CHECKING\nfrom unittest.mock import create_autospec\n\nif TYPE_CHECKING:\n    from foo import Foo\n\ndef bar(x: Foo) -\u003e None:\n    pass\n\ncreate_autospec(bar)\n```\n\nThis will result in `NameError: name 'Foo' is not defined` because `_get_signature_object` in `unittest.mock` calls `inspect.signature` without explicitly passing `annotation_format`, so it defaults to `Format.VALUE`.\n\nSince `create_autospec` really shouldn't care whether or not the annotations can be evaluated at runtime on the given object, I would suggest switching over to `Format.FORWARDREF` or `Format.STRING`, so autospeccing continues to work in Python 3.14+ for people that used to rely on `from __future__ import annotations` and now want to switch to PEP 649 semantics, without needing to change their code.\n\n### CPython versions tested on:\n\n3.14\n\n### Operating systems tested on:\n\nLinux\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-145756\n* gh-146191\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/Daverball","@type":"Person","name":"Daverball"},"datePublished":"2026-03-10T14:39:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/145754/cpython/issues/145754"}