The current CI warning system works well at catching all new warnings on that platform. Unfortunately it presents too high a burden developing new code or altering existing code to use Python warnings in a standard way if that code is in a widely used area.
I hit this situation trying to add warnings to filter/basis calcs. This use case would have required altering most unit tests that used basis+filters ... (way too many, and would continue on into future work).
Probably the system should be reconsidered towards a design where developers can add standard Pythonic warnings without a lot of additional work, while still catching new (external) warnings.
The current CI warning system works well at catching all new warnings on that platform. Unfortunately it presents too high a burden developing new code or altering existing code to use Python warnings in a standard way if that code is in a widely used area.
I hit this situation trying to add warnings to filter/basis calcs. This use case would have required altering most unit tests that used basis+filters ... (way too many, and would continue on into future work).
Probably the system should be reconsidered towards a design where developers can add standard Pythonic warnings without a lot of additional work, while still catching new (external) warnings.