Update dependency loguru to v0.7.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
loguru (changelog)	==0.5.3 → ==0.7.3

---

Release Notes

Delgan/loguru (loguru)

v0.7.3

Compare Source

=====================

• Fix Cython incompatibility caused by the absence of underlying stack frames, which resulted in a ValueError during logging (#&#8203;88 <https://github.com/Delgan/loguru/issues/88>_).
• Fix possible RuntimeError when removing all handlers with logger.remove() due to thread-safety issue (#&#8203;1183 <https://github.com/Delgan/loguru/issues/1183>, thanks @jeremyk <https://github.com/jeremyk>).
• Fix diagnose=True option of exception formatting not working as expected with Python 3.13 (#&#8203;1235 <https://github.com/Delgan/loguru/issues/1235>, thanks @etianen <https://github.com/etianen>).
• Fix non-standard level names not fully compatible with logging.Formatter() (#&#8203;1231 <https://github.com/Delgan/loguru/issues/1231>, thanks @yechielb2000 <https://github.com/yechielb2000>).
• Fix inability to display a literal "\" immediately before color markups (#&#8203;988 <https://github.com/Delgan/loguru/issues/988>_).
• Fix possible infinite recursion when an exception is raised from a __repr__ method decorated with logger.catch() (#&#8203;1044 <https://github.com/Delgan/loguru/issues/1044>_).
• Improve performance of datetime formatting while logging messages (#&#8203;1201 <https://github.com/Delgan/loguru/issues/1201>, thanks @trim21 <https://github.com/trim21>).
• Reduce startup time in the presence of installed but unused IPython third-party library (#&#8203;1001 <https://github.com/Delgan/loguru/issues/1001>, thanks @zakstucke <https://github.com/zakstucke>).

v0.7.2

Compare Source

=====================

• Add support for formatting of ExceptionGroup errors (#&#8203;805 <https://github.com/Delgan/loguru/issues/805>_).
• Fix possible RuntimeError when using multiprocessing.set_start_method() after importing the logger (#&#8203;974 <https://github.com/Delgan/loguru/issues/974>_).
• Fix formatting of possible __notes__ attached to an Exception (#&#8203;980 <https://github.com/Delgan/loguru/issues/980>_).

v0.7.1

Compare Source

=====================

• Add a new context optional argument to logger.add() specifying multiprocessing context (like "spawn" or "fork") to be used internally instead of the default one (#&#8203;851 <https://github.com/Delgan/loguru/issues/851>_).
• Add support for true colors on Windows using ANSI/VT console when available (#&#8203;934 <https://github.com/Delgan/loguru/issues/934>, thanks @tunaflsh <https://github.com/tunaflsh>).
• Fix possible deadlock when calling logger.complete() with concurrent logging of an asynchronous sink (#&#8203;906 <https://github.com/Delgan/loguru/issues/906>_).
• Fix file possibly rotating too early or too late when re-starting an application around midnight (#&#8203;894 <https://github.com/Delgan/loguru/issues/894>_).
• Fix inverted "<hide>" and "<strike>" color tags (#&#8203;943 <https://github.com/Delgan/loguru/pull/943>, thanks @tunaflsh <https://github.com/tunaflsh>).
• Fix possible untraceable errors raised when logging non-unpicklable Exception instances while using enqueue=True (#&#8203;329 <https://github.com/Delgan/loguru/issues/329>_).
• Fix possible errors raised when logging non-picklable Exception instances while using enqueue=True (#&#8203;342 <https://github.com/Delgan/loguru/issues/342>, thanks @ncoudene <https://github.com/ncoudene>).
• Fix missing seconds and microseconds when formatting timezone offset that requires such accuracy (#&#8203;961 <https://github.com/Delgan/loguru/issues/961>_).
• Raise ValueError if an attempt to use nanosecond precision for time formatting is detected (#&#8203;855 <https://github.com/Delgan/loguru/issues/855>_).

v0.7.0

Compare Source

=====================

• Update InterceptHandler recipe to make it compatible with Python 3.11 (#&#8203;654 <https://github.com/Delgan/loguru/issues/654>_).
• Add a new watch optional argument to file sinks in order to automatically re-create possibly deleted or changed file (#&#8203;471 <https://github.com/Delgan/loguru/issues/471>_).
• Make patch() calls cumulative instead of overriding the possibly existing patching function (#&#8203;462 <https://github.com/Delgan/loguru/issues/462>_).
• Make sinks added with enqueue=True and catch=False still process logged messages in case of internal exception (#&#8203;833 <https://github.com/Delgan/loguru/issues/833>_).
• Avoid possible deadlocks caused by re-using the logger inside a sink, a signal handler or a __del__ method. Since the logger is not re-entrant, such misuse will be detected and will now generate a RuntimeError (#&#8203;712 <https://github.com/Delgan/loguru/issues/712>, thanks @jacksmith15 <https://github.com/jacksmith15>).
• Fix file sink rotation using an aware datetime.time for which the timezone was ignored (#&#8203;697 <https://github.com/Delgan/loguru/issues/697>_).
• Fix logs colorization not automatically enabled for Jupyter Notebook and Google Colab (#&#8203;494 <https://github.com/Delgan/loguru/issues/494>_).
• Fix logs colorization not automatically enabled for Github Actions and others CI platforms (#&#8203;604 <https://github.com/Delgan/loguru/issues/604>_).
• Fix logger.complete() possibly hanging forever when enqueue=True and catch=False if internal thread killed due to Exception raised by sink (#&#8203;647 <https://github.com/Delgan/loguru/issues/647>_).
• Fix incompatibility with freezegun library used to simulate time (#&#8203;600 <https://github.com/Delgan/loguru/issues/600>_).
• Raise exception if logger.catch() is used to wrap a class instead of a function to avoid unexpected behavior (#&#8203;623 <https://github.com/Delgan/loguru/issues/623>_).

v0.6.0

Compare Source

=====================

• Remove internal use of pickle.loads() to fix the (finally rejected) security vulnerability referenced as CVE-2022-0329 <https://nvd.nist.gov/vuln/detail/CVE-2022-0329>_ (#&#8203;563 <https://github.com/Delgan/loguru/issues/563>_).
• Modify coroutine sink to make it discard log messages when loop=None and no event loop is running (due to internally using asyncio.get_running_loop() in place of asyncio.get_event_loop()).
• Remove the possibility to add a coroutine sink with enqueue=True if loop=None and no event loop is running.
• Change default encoding of file sink to be utf8 instead of locale.getpreferredencoding() (#&#8203;339 <https://github.com/Delgan/loguru/issues/339>_).
• Prevent non-ascii characters to be escaped while logging JSON message with serialize=True (#&#8203;575 <https://github.com/Delgan/loguru/pull/575>, thanks @ponponon <https://github.com/ponponon>).
• Fix flake8 errors and improve code readability (#&#8203;353 <https://github.com/Delgan/loguru/issues/353>, thanks @AndrewYakimets <https://github.com/AndrewYakimets>).

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.