-
Notifications
You must be signed in to change notification settings - Fork 78
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
40+ pytest warnings add friction to testing #157
Comments
I realized that I shouldn't have closed until I have tested that it's working without needing the So, reopening. I'm running the test now. Will update when done. |
I'm also confused about that new |
Agreed. I just realized that since that's a different issue than this issue, I created a new issue. #166 So now we can close this issue. |
Is your feature request related to a problem? Please describe.
When I go to run even a single unit test, I get 40 warnings, all deprecation warnings. (Examples below). It makes it really hard to wade through to get to what actually matters - the errors, and non-deprecation warnings.
The warnings are for 3rd party packages related to python3.8. Not really in our control, and they'll get better on their own in the next 6-12 months anyway.
Describe the solution you'd like
Explicitly disable just specific warnings of these 3rd party packages for py 3.8. Other warnings should be kept on (good hygiene).
Example warnings
The text was updated successfully, but these errors were encountered: