certbot/pytest.ini

# This file isn't used while testing packages in tools/_release.sh so any
# settings we want to also change there must be added to the release script
# directly.
[pytest]
# In general, all warnings are treated as errors. Here are the exceptions:
#   1- decodestring: https://github.com/rthalley/dnspython/issues/338
#   2- Python 2 deprecation: https://github.com/certbot/certbot/issues/8388
#      (to be removed with Certbot 1.12.0 and its drop of Python 2 support)
# 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
    ignore:Python 2 support will be dropped:PendingDeprecationWarning
Don't use pytest.ini during the release. (#6550) Currently the release script in master fails for a few reasons. First, it's trying to use --numprocesses which comes from a pytest plugin that we're not installing in the release script. Second, many new warnings are raised when we're not using pinned versions of our dependencies. I'm not sure I agree, but one could argue that we should fix these issues and use the file during the release. I'm particularly hesitant for us to do this when it comes to warnings. We currently do not pin our dependencies in the release script. Do we really want to stop the release because a new package was released and is warning about something? One could argue we do because these warnings may be visible to the user, but they very rarely are and I think this makes the release process much too painful. I especially do not think we should block the release on this now as we are not up to date on the warnings raised by the latest versions of our packages so there is a lot to work through. * Don't use pytest.ini during the release. * State that pytest.ini isn't used in release script. 2018-11-30 20:40:55 -05:00			`# This file isn't used while testing packages in tools/_release.sh so any`
			`# settings we want to also change there must be added to the release script`
			`# directly.`
move values to pytest.ini 2018-07-11 20:25:48 -04:00			`[pytest]`
Allow to execute a tox target without pinned dependencies (#6590) This PR passes the CERTBOT_NO_PIN environment variable to the unit tests tox envs. By setting CERTBOT_NO_PIN to 1 before executing a given tox env, certbot dependencies will be installed at their latest version instead of the usual pinned version. I also moved the unpin logic one layer below to allow it to be used potentially more widely, and avoid unnecessary merging constraints operation in this case. As warnings are errors now, latest versions of Python will break now the tests, because collections launch a warning when some classes are imported from collections instead of collections.abc. Certbot code is patched, and warning is ignored for now, because a lot of third party libraries still depend on this behavior. * Allow to execute a tox target without pinned dependencies * Correct lint * Retrigger build. * Remove debug code * Added test against unpinned dependencies from test-everything-unpinned-dependencies branch * Remove duplicated assertion to pass TRAVIS and APPVEYOR in default tox environment. 2019-01-17 16:02:35 -05:00			`# In general, all warnings are treated as errors. Here are the exceptions:`
			`# 1- decodestring: https://github.com/rthalley/dnspython/issues/338`
Deprecate support for Python 2 (#8491) Fixes #8388 * Deprecate support for Python 2 * Ignore deprecation warning * Update certbot/CHANGELOG.md Co-authored-by: Brad Warren <bmw@users.noreply.github.com> 2020-12-08 15:19:42 -05:00			`# 2- Python 2 deprecation: https://github.com/certbot/certbot/issues/8388`
			`# (to be removed with Certbot 1.12.0 and its drop of Python 2 support)`
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 2020-05-04 19:54:09 -04:00			`# 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.`
Only error on DeprecationWarnings 2018-10-30 20:13:40 -04:00			`filterwarnings =`
Move back to using a warning whitelist 2018-10-30 20:24:29 -04:00			`error`
remove pytest.mark, move to specific ignore in pytest.ini 2018-11-05 20:41:26 -05:00			`ignore:decodestring:DeprecationWarning`
Deprecate support for Python 2 (#8491) Fixes #8388 * Deprecate support for Python 2 * Ignore deprecation warning * Update certbot/CHANGELOG.md Co-authored-by: Brad Warren <bmw@users.noreply.github.com> 2020-12-08 15:19:42 -05:00			`ignore:Python 2 support will be dropped:PendingDeprecationWarning`