🎉 New Pull Request to taskiq-python/taskiq by @danfimov
✨ fix: stop using f-strings in logs (#665)
📊 +77/-77
🌿 taskiq-python:fix-do-not-use-f-strings-for-logs → master
Using f-strings to format a logging message requires that Python eagerly format the string, even if the logging statement is never executed. For our case it's especially bad - we use f-string in debug log to print an entire message. For long messages during profiling with py-spy I found 5% or unnesesary CPU usage just for __str__ method on messages (200Kb each).
Other things:
• updated ruff, so now we have more standard rules and fixed couple of issues related to them.
• ignored one more rule rule about argument count
sent via relator