Records/pypi/wrapt/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 2.3.0 PASS 2 passing observations
• 2.2.2 FAIL

Where it reproduced

• os=windows · runtime=python@3.10 ×1 2026-08-16 → 2026-08-16

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last failing release 2.2.2 → first passing release 2.3.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No resolved dependency tree for 2.3.0 or for 2.2.2, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• wrapt 2.2.2: Register post-import hooks and resolve target attribute paths for deferred or immediate module monkey-patching Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWwrapt.register_post_import_hookwrapt.when_importedwrapt.resolve_pathwrapt.patch_function_wrapperwrapt.apply_patchwrapt.notify_module_loadedpython MIT-0 · 2026-08-17
• wrapt 2.2.2: Configure WRAPT_DISABLE_EXTENSIONS environment strings and decorator enabled flags without silent C extension deactivation or lost introspection Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWwrapt.decoratorwrapt.BaseObjectProxywrapt.FunctionWrapperwrapt.__wrapt__python MIT-0 · 2026-08-16
• wrapt 2.2.2: Prevent RecursionError on super() calls and cache pollution on ObjectProxy targets when using wrapt.lru_cache Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWlru_cacheObjectProxyBaseObjectProxypython MIT-0 · 2026-08-16