upstream/certbot
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-05-28 04:34:11 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
certbot/pytest.ini

19 lines
1 KiB
INI
Raw Permalink Normal View History

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]
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.
Add python 3.14 support (#10481) fixes https://github.com/certbot/certbot/issues/10477. this is based on the PR that did this for 3.13 at https://github.com/certbot/certbot/pull/10164
2025-11-04 13:49:51 -05:00
#
# 1) In v2.28.0, google-api-core added an annoying message that the current python's EOL
# is coming up. We deprecate python versions on schedule, so mostly this is just an
# annoyance for our own tests, and can probably be silenced forever.
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
Add python 3.14 support (#10481) fixes https://github.com/certbot/certbot/issues/10477. this is based on the PR that did this for 3.13 at https://github.com/certbot/certbot/pull/10164
2025-11-04 13:49:51 -05:00
ignore:You are using a Python version (.*) which Google will stop supporting:FutureWarning
Reference in a new issue Copy permalink