Antoine, it's not a wishy-washy compromise, it's a compromise based on the fact that code that has been factored out to a support module is far more likely to have a test suite than code that's directly in __main__.
Thus the logic for the revised default filters is as follows:
* code running in __main__ will see deprecation warnings when it runs
* code running outside __main__ will see deprecation warnings when its test suite runs
If someone is publishing code that's not in a main module, and they *don't* have a test suite for that code yet, then they have bigger problems to worry about than not seeing deprecation warnings.