[ddehilster]

An NLP++ analyzer whose loop never ends could only be stopped by killing the process. One that makes a new string every turn gets there by itself, by running out of memory: in production, one such grammar took a document extractor down five times in half an hour. Engine 4.2.41 (VisualText/nlp-engine#800, released in 4.2.42 / NLPPlus 2.2.73) can stop a run at a time limit. This passes the limit through.

API

• Engine.analyze(..., timeout=seconds) and NLPPlus.analyze(..., timeout=). None, the default, means no limit, as before.
• A run stopped at the limit raises AnalysisStopped, which carries the analyzer name and the timeout. It's an EngineException and also an Exception, so ordinary except Exception handling catches it. EngineException alone wouldn't be caught, because it derives from BaseException.
• The binding takes timeout in analyze() and exposes last_run_stopped().

The engine stops the run at its next while turn or pass, skips the passes after it, and frees what it built, so the same Engine is fit for the next call.

Tests: TimeoutTest builds a throwaway analyzer that loops forever, and checks that:

• it's stopped within the limit;
• AnalysisStopped is raised and is an Exception;
• the pass after the loop didn't run;
• the same Engine then runs an analyzer that finishes, with and without a timeout.

Run locally against this engine on Windows, all three pass. The four other tests that fail locally (test_simple, test_emailaddress_parser, test_repeated_analyze_same_process, test_multibyte_words_survive_single_byte_locale) fail the same way on an unmodified main built the same way, so they're about the local environment, not this change. CI here is the real check.

🤖 Generated with Claude Code