Ripping out ridiculous 'always' warning filter #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
warnings.simplefilter('always')
storages
package, but to the entire Django project in which it's being used.For example, the project I work on uses Django's
strip_tags()
function to create thetext/plain
part of multipart emails, and when using Django 1.6 and Python 3.3+, there are twoDeprecationWarning
s about impending changes to theHTMLParser
API whenstrip_tags()
is used:These usages live in the Django codebase and are out of my control. Without
django-storages-redux
installed, I see these warnings once at the beginning of my unit test runs. After installingdjango-storages-redux
, I see these warnings for nearly every test (almost 2,000 tests --> almost 4,000 warnings printed).