Use more performant version of Python logging calls

[madscientist]

No description provided.

[codecov-commenter]

Codecov Report

Patch coverage: 6.06% and no project coverage change.

Comparison is base (fb5f845) 34.83% compared to head (31310c4) 34.83%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1205   +/-   ##
=======================================
  Coverage   34.83%   34.83%           
=======================================
  Files          44       44           
  Lines        7949     7949           
  Branches     1072     1072           
=======================================
  Hits         2769     2769           
  Misses       5068     5068           
  Partials      112      112           

Files Changed	Coverage Δ
atlassian/bitbucket/__init__.py	29.96% <0.00%> (ø)
atlassian/confluence.py	13.23% <0.00%> (ø)
atlassian/jira.py	19.92% <0.00%> (ø)
atlassian/rest_client.py	68.04% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gonchik]

@madscientist what achievement we can get from that notation?

[madscientist]

Basically, the logging string is not formatted until/unless the log message is going to be emitted. So for, for example, debug() messages which are rarely if ever actually emitted to a log sink, this means Python doesn't have to allocate the string and format it all. See for info https://docs.python.org/3/library/logging.html#logging.debug

If you use .format() then the formatted string is constructed by the calling function before the logger even gets to see it, so it cannot avoid the formatting even if the resulting formatted string is just dropped on the floor.

[gonchik]

Thanks for explanation :) @madscientist