René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"configure warnings as errors in the test suite","articleBody":"# Feature or enhancement\n\n### Proposal:\n\nIt's very easy (especially when deprecating something) to introduce a lot of noisy test output with new warnings, eg: https://github.com/python/cpython/issues/127949#issuecomment-2558227488\n\nI think it would be useful to either configure warnings as errors in the test suite (and then capture unraisable/threadexcept errors using a mechanism like pytest has) or tee any warnings produced, and fail CI if any have been produced that were not captured with catch_warnings or assertWarns etc like https://pypi.org/project/pytest-max-warnings/\n\n### Has this already been discussed elsewhere?\n\nI have already discussed this feature proposal on Discourse\n\n### Links to previous discussion of this feature:\n\nhttps://discuss.python.org/t/its-too-easy-to-introduce-noise-in-cpythons-test-suite-output-resourcewarnings-and-deprecationwarnings/75234\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-128726\n* gh-128906\n* gh-128935\n* gh-128936\n* gh-128973\n* gh-129179\n* gh-131802\n* gh-131824\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/graingert","@type":"Person","name":"graingert"},"datePublished":"2025-01-13T07:57:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/128770/cpython/issues/128770"}