-
-
Notifications
You must be signed in to change notification settings - Fork 343
refactor warnings #3098
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
refactor warnings #3098
Conversation
👍 to having our own zarr warning sub-classes, I think I'm 👎 on having some of our own warning silencing helpers, but depends on what the proposal is I guess. So would be good to have separate PRs for those. |
I amended the PR description to remove the goal of providing top-level functions for users to silence zarr warnings. For now, users can use the built-in warnings library to control warnings. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3098 +/- ##
===========================================
- Coverage 94.76% 60.54% -34.23%
===========================================
Files 78 78
Lines 8710 8716 +6
===========================================
- Hits 8254 5277 -2977
- Misses 456 3439 +2983
🚀 New features to boost your workflow:
|
closes #3096
this PR adds zarr-specific subclasses of
FutureWarning
andDeprecationWarning
,so that we can expose routines for silencing future / deprecation warnings specifically emitted by zarr-python.This PR is a draft until I add the silencing routines later in this PR.