Repository navigation
Capture expected deprecation warnings in entry-point tests #581
Description
Activity
Hi @claell — I'm posting this same note on all of your July 16 issues and PRs (#567–#597), so apologies for the form-letter feel.
I'm closing this. The batch — 13 issues, 18 PRs, ~3,000 lines, opened within a two-hour window with spec-style language and forward-references to PR numbers that didn't exist yet — reads as AI-generated rather than something you hit and verified by hand. Reviewing it properly would cost me more time than just fixing the parser myself.
If this is a real bug you've actually hit: reopen it with a concrete repro and a small, human-verified fix, and I'll review it. Any nontrivial design or API choice should be discussed in the issue first, before code is written. Otherwise, please disclose and verify AI-assisted contributions before submitting them in future.
Problem
Four entry-point tests intentionally pass both a deprecated parameter and its replacement to verify the resulting conflict error. The tests assert the
ValueError, but they do not capture the expectedDeprecationWarningemitted first.Consequently, a normal suite run reports four warnings and the suite cannot be run with warnings treated as errors, even though these warnings are part of the behavior under test rather than unexamined application output.
Proposed coverage
Wrap the four conflict cases in
pytest.warns(DeprecationWarning)while retaining the existing error-message assertions. This documents both parts of the contract and permits warning-strict test execution without changing production behavior.