diff options
| author | Brad Warren <bmw@users.noreply.github.com> | 2020-05-05 02:54:09 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-05 02:54:09 +0300 |
| commit | ac2d691ade1e86595502d6603afc8a7853f4acfe (patch) | |
| tree | 07f711db17b5bbdae807325ea1ff274bc872b539 /pytest.ini | |
| parent | 5536c912238d96b15295a1b6938472fd24cf40ce (diff) | |
Add warning about ignoring our own warnings (#7971)
Coming out of the conversation at #7863 in the linked Google Doc, we should always have at least 1 release between updating one of our plugins to stop using a deprecated acme/certbot API and removing it from acme/certbot. Doing this gives the plugin changes time to propagate rather than potentially having the plugin break because Certbot was updated before the plugin had made the necessary changes.
This comment here should help ensure this.
* Add pytest warnings warning.
* clarify comment
Diffstat (limited to 'pytest.ini')
| -rw-r--r-- | pytest.ini | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/pytest.ini b/pytest.ini index e09813e52..16aa9a193 100644 --- a/pytest.ini +++ b/pytest.ini @@ -4,6 +4,13 @@ [pytest] # In general, all warnings are treated as errors. Here are the exceptions: # 1- decodestring: https://github.com/rthalley/dnspython/issues/338 +# Warnings being triggered by our plugins using deprecated features in +# acme/certbot should be fixed by having our plugins no longer using the +# deprecated code rather than adding them to the list of ignored warnings here. +# Fixing things in this way prevents us from shipping packages raising our own +# deprecation warnings and gives time for plugins that don't use the deprecated +# API to propagate, especially for plugins packaged as an external snap, before +# we release breaking changes. filterwarnings = error ignore:decodestring:DeprecationWarning |