+ lHj:Rt^RIHt^RIt^RIHtRRRlltR#)uShared interpreter-shutdown predicate for background threads that can outlive process teardown (cron delivery, concurrent tool submission, retry paths). Once finalization starts, ``concurrent.futures`` refuses new work and asyncio's default executor is gone, so any further scheduling only produces noise (stray prints after the TUI exited, tracebacks in ``errors.log``, futile retries). CPython raises ``cannot schedule new futures after interpreter shutdown`` (module-global flag) or ``... after shutdown`` (a pool whose ``shutdown()`` ran); the short prefix catches both — safe here because every pool involved is a module-global daemon or a ``with``-scoped local only finalization can shut down. ) annotationsN)Optionalc V^8dQhRRRR/#)exczOptional[BaseException]returnbool)formats"?/home/ubuntu/.hermes/hermes-agent/tools/interpreter_shutdown.py __annotate__r sQQ#:QdQc\P!4'dR#VRJ;'dR\V4P49#)zTrue when the interpreter is finalizing. ``exc`` lets a caller treat an already-raised scheduling error as a shutdown signal: the ``concurrent.futures`` flag can be set a hair before ``sys.is_finalizing()`` flips.TNzcannot schedule new futures)sys is_finalizingstrlower)rs&r interpreter_shutting_downrs9  d? P P<C@PPPr )N)__doc__ __future__rrtypingrrr r r rs! # QQr