Skip to content

Commit

Permalink
No commit message
Browse files Browse the repository at this point in the history
  • Loading branch information
max-sixty committed Apr 28, 2024
1 parent dd2548e commit 72bfc9f
Showing 1 changed file with 9 additions and 7 deletions.
16 changes: 9 additions & 7 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -286,17 +286,19 @@ addopts = ["--strict-config", "--strict-markers"]
# We want to forbid warnings from within xarray in our tests — instead we should
# fix our own code, or mark the test itself as expecting a warning. So this:
# - Converts any warning from xarray into an error
# - Ignores warnings which the test suite currently raises; since it wasn't
# - practical to fix them all before merging this config. We can remove these
# over time -- if you see a warning that we now handle, remove the exception.
# If you are up for a small contribution, find the warning and fix it! The
# warnings are still listed (`default`, not `ignore`).
# - Allows some warnings ("default") which the test suite currently raises,
# since it wasn't practical to fix them all before merging this config. The
# arnings are still listed in CI (since it uses `default`, not `ignore`).
#
# We can remove these rules allowing warnings; a valued contribution is removing
# a line, seeing what breaks, and then fixing the library code or tests so that
# it doesn't raise warnings.
#
# While we only raise an error on warnings from within xarray, if dependency
# raises a warning with a stacklevel such that it's interpreted to be raised
# from xarray, please feel free to ignore it here.
# from xarray, please feel free to add a rule switching it to `default` here.
#
# If this gets in the way of making progress, it's also acceptable to
# If these settings get in the way of making progress, it's also acceptable to
# temporarily add additional ignores.

filterwarnings = [
Expand Down

0 comments on commit 72bfc9f

Please sign in to comment.