-
Notifications
You must be signed in to change notification settings - Fork 636
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
Unnecessary warning messages #1335
Comments
I see it the same way, this should never be more then an info, maybe just trace/debug. Library users, who call the API multiple times (may by an automatism, that updates 500 issues), get flooded with warnings, which are none. So finding the real problems gets hard. |
It some cases these warnings make sense for example in confluence.py: |
This warning doesn't make sense sind python warns already about the deprecation. |
Hello!
Warning level logging is way too chatty even in %100 success cases. There are multiple examples where the method attempts what it exactly needs to do - but library still prints a warning log. Some examples are:
https://github.com/atlassian-api/atlassian-python-api/blob/master/atlassian/jira.py#L1344
https://github.com/atlassian-api/atlassian-python-api/blob/master/atlassian/jira.py#L1394
https://github.com/atlassian-api/atlassian-python-api/blob/master/atlassian/jira.py#L1400
...
So from my POV if a method does an update of an issue, it is not a warning that it is updating an issue - am I somewhat wrong?
Thanks!
Celal
The text was updated successfully, but these errors were encountered: