-
-
Notifications
You must be signed in to change notification settings - Fork 471
Open
Labels
affects: dxRelated to developer experienceRelated to developer experienceaffects: technical debtImproves the state of the codebaseImproves the state of the codebasereadyReady for implementationReady for implementationtemp: checkThis issue needs to be double-checked for relevance - Oct 2025 backlog grooming.This issue needs to be double-checked for relevance - Oct 2025 backlog grooming.type: bugwork: backendRelated to Python, Django, and simple SQLRelated to Python, Django, and simple SQL
Milestone
Description
Description
Currently, running the test suite generates 1126 warnings for me. This means any valid ones are missed, and it generally makes the output of the test suite pretty useless when run with -svv to see actual problems.
Expected behavior
The test suite should not generate this many warnings (maybe none)
We should use a combination of
- filtering warnings we expect (e.g.,
UserWarnings when we're testing our own warnings) in pytest - filtering 3rd party warnings (e.g.,
DeprecationWarnings) in pytest - cleaning up code that generates warnings to avoid causing them, or filtering them if needed.
To Reproduce
Run the test suite with -svv set. Witness the horror.
Additional context
Helpful links for how to deal with the warnings in pytest:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
affects: dxRelated to developer experienceRelated to developer experienceaffects: technical debtImproves the state of the codebaseImproves the state of the codebasereadyReady for implementationReady for implementationtemp: checkThis issue needs to be double-checked for relevance - Oct 2025 backlog grooming.This issue needs to be double-checked for relevance - Oct 2025 backlog grooming.type: bugwork: backendRelated to Python, Django, and simple SQLRelated to Python, Django, and simple SQL