[RonnyPfannschmidt]

Requested by Ronny · project thread

🤖 Written by Claude Opus 5.5 via Claude Code for the pytest maintainers; I prompted it, it did the work, I read it.

closes #15281

_find_wrapped_fixture_def (added in #13745) used inspect.unwrap, whose depth limit is sys.getrecursionlimit(). unittest.mock.call returns a new _Call for every attribute, including __wrapped__, and it got past the mock guard because its _mock_name is None. Once a conftest or library raised the recursion limit (to 100 000, for example), collection followed that chain until memory ran out. On main the reproducer from the issue gets OOM-killed.

Changes:

• The mock guard uses NOTSET as the sentinel instead of None, so any object that has a _mock_name attribute is skipped, mock.call included.
• __wrapped__ is walked by a local loop capped at 100 steps (_MAX_UNWRAP_DEPTH), with id-based loop detection. This makes the cost independent of the recursion limit for other proxies that grow a fresh __wrapped__ on every access.

Tests:

• An end-to-end subprocess test using the issue's reproducer.
• A unit test that checks the depth cap on an endless __wrapped__ chain.
• A unit test that checks mock.call and Mock() are skipped.

The first two fail without the fix. The full suite and pre-commit pass locally.

• Include new tests or update existing tests when applicable.
• Allow maintainers to push and squash when merging my commits.
• If AI agents were used, they are credited in Co-authored-by commit trailers.
• Create a new changelog file in the changelog directory.

---

Generated by Claude Code

[bluetech]

I haven't reviewed 264846d but it seems pretty complex, and this seems to make it even more complex. Have you considered reverting the change instead? 9.2.0 is still new so I think a revert would be fine.