-
Notifications
You must be signed in to change notification settings - Fork 119
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
Treat warnings as errors in pytests #168
Conversation
CI builds with this would be good. |
As mentioned in a separate discussion, it might be better to make the default value OFF so it doesn't disrupt current users. If we do this, then we should go through all our packages and turn the feature on explicitly to get this in our CI builds (unless I'm missing something). The downside is that it's easy to forget to turn on for new packages. I don't feel strongly either way, so I can change the default if someone has a preference. |
Imo sticking to defaults makes more sense. And if the calling code wants to escalate warnings then they should opt-in to that (same as e.g. the compiler flag with the same name). |
This has the benefit of making deprecation warnings visible, which are not by default. Signed-off-by: Jacob Perron <jacob@openrobotics.org>
Signed-off-by: Jacob Perron <jacob@openrobotics.org>
Signed-off-by: Jacob Perron <jacob@openrobotics.org>
Signed-off-by: Jacob Perron <jacob@openrobotics.org>
a878a9a
to
73d7a6c
Compare
This has the benefit of making deprecation warnings visible, which are not by default.