Bump loguru from 0.4.1 to 0.5.3

[dependabot]

Bumps loguru from 0.4.1 to 0.5.3.

Release notes

Sourced from loguru's releases.

0.5.3

• Fix child process possibly hanging at exit while combining enqueue=True with third party library like uwsgi (#309, thanks @​dstlmrk).
• Fix possible exception during formatting of non-string messages (#331).

0.5.2

• Fix AttributeError within handlers using serialize=True when calling logger.exception() outside of the context of an exception (#296).
• Fix error while logging an exception containing a non-picklable value to a handler with enqueue=True (#298).
• Add support for async callable classes (with __call__ method) used as sinks (#294, thanks @​jessekrubin).

0.5.1

• Modify the way the extra dict is used by LogRecord in order to prevent possible KeyError with standard logging handlers (#271).
• Add a new default optional argument to logger.catch(), it should be the returned value by the decorated function in case an error occurred (#272).
• Fix ValueError when using serialize=True in combination with logger.catch() or logger.opt(record=True) due to circular reference of the record dict (#286).

0.5.0

• Remove the possibility to modify the severity no of levels once they have been added in order to prevent surprising behavior (#209).
• Add better support for "structured logging" by automatically adding **kwargs to the extra dict besides using these arguments to format the message. This behavior can be disabled by setting the new .opt(capture=False) parameter (#2).
• Add a new onerror optional argument to logger.catch(), it should be a function which will be called when an exception occurs in order to customize error handling (#224).
• Add a new exclude optional argument to logger.catch(), is should be a type of exception to be purposefully ignored and propagated to the caller without being logged (#248).
• Modify complete() to make it callable from non-asynchronous functions, it can thus be used if enqueue=True to make sure all messages have been processed (#231).
• Fix possible deadlocks on Linux when multiprocessing.Process() collides with enqueue=True or threading (#231).
• Fix compression function not executable concurrently due to file renaming (to resolve conflicts) being performed after and not before it (#243).
• Fix the filter function listing files for retention being too restrictive, it now matches files based on the pattern "basename(.*).ext(.*)" (#229).
• Fix the impossibility to remove() a handler if an exception is raised while the sink' stop() function is called (#237).
• Fix file sink left in an unstable state if an exception occurred during retention or compression process (#238).
• Fix situation where changes made to record["message"] were unexpectedly ignored when opt(colors=True), causing "out-of-date" message to be logged due to implementation details (#221).
• Fix possible exception if a stream having an isatty() method returning True but not being compatible with colorama is used on Windows (#249).
• Fix exceptions occurring in coroutine sinks never retrieved and hence causing warnings (#227).

Changelog

Sourced from loguru's changelog.

0.5.3_ (2020-09-20)

• Fix child process possibly hanging at exit while combining enqueue=True with third party library like uwsgi ([#309](https://github.com/Delgan/loguru/issues/309) <https://github.com/Delgan/loguru/issues/309>, thanks @dstlmrk <https://github.com/dstlmrk>).
• Fix possible exception during formatting of non-string messages ([#331](https://github.com/Delgan/loguru/issues/331) <https://github.com/Delgan/loguru/issues/331>_).

0.5.2_ (2020-09-06)

• Fix AttributeError within handlers using serialize=True when calling logger.exception() outside of the context of an exception ([#296](https://github.com/Delgan/loguru/issues/296) <https://github.com/Delgan/loguru/issues/296>_).
• Fix error while logging an exception containing a non-picklable value to a handler with enqueue=True ([#298](https://github.com/Delgan/loguru/issues/298) <https://github.com/Delgan/loguru/issues/298>_).
• Add support for async callable classes (with __call__ method) used as sinks ([#294](https://github.com/Delgan/loguru/issues/294) <https://github.com/Delgan/loguru/pull/294>, thanks @jessekrubin <https://github.com/jessekrubin>).

0.5.1_ (2020-06-12)

• Modify the way the extra dict is used by LogRecord in order to prevent possible KeyError with standard logging handlers ([#271](https://github.com/Delgan/loguru/issues/271) <https://github.com/Delgan/loguru/issues/271>_).
• Add a new default optional argument to logger.catch(), it should be the returned value by the decorated function in case an error occurred ([#272](https://github.com/Delgan/loguru/issues/272) <https://github.com/Delgan/loguru/issues/272>_).
• Fix ValueError when using serialize=True in combination with logger.catch() or logger.opt(record=True) due to circular reference of the record dict ([#286](https://github.com/Delgan/loguru/issues/286) <https://github.com/Delgan/loguru/issues/286>_).

0.5.0_ (2020-05-17)

• Remove the possibility to modify the severity no of levels once they have been added in order to prevent surprising behavior ([#209](https://github.com/Delgan/loguru/issues/209) <https://github.com/Delgan/loguru/issues/209>_).
• Add better support for "structured logging" by automatically adding **kwargs to the extra dict besides using these arguments to format the message. This behavior can be disabled by setting the new .opt(capture=False) parameter ([#2](https://github.com/Delgan/loguru/issues/2) <https://github.com/Delgan/loguru/issues/2>_).
• Add a new onerror optional argument to logger.catch(), it should be a function which will be called when an exception occurs in order to customize error handling ([#224](https://github.com/Delgan/loguru/issues/224) <https://github.com/Delgan/loguru/issues/224>_).
• Add a new exclude optional argument to logger.catch(), is should be a type of exception to be purposefully ignored and propagated to the caller without being logged ([#248](https://github.com/Delgan/loguru/issues/248) <https://github.com/Delgan/loguru/issues/248>_).
• Modify complete() to make it callable from non-asynchronous functions, it can thus be used if enqueue=True to make sure all messages have been processed ([#231](https://github.com/Delgan/loguru/issues/231) <https://github.com/Delgan/loguru/issues/231>_).
• Fix possible deadlocks on Linux when multiprocessing.Process() collides with enqueue=True or threading ([#231](https://github.com/Delgan/loguru/issues/231) <https://github.com/Delgan/loguru/issues/231>_).
• Fix compression function not executable concurrently due to file renaming (to resolve conflicts) being performed after and not before it ([#243](https://github.com/Delgan/loguru/issues/243) <https://github.com/Delgan/loguru/issues/243>_).
• Fix the filter function listing files for retention being too restrictive, it now matches files based on the pattern "basename(.*).ext(.*)" ([#229](https://github.com/Delgan/loguru/issues/229) <https://github.com/Delgan/loguru/issues/229>_).
• Fix the impossibility to remove() a handler if an exception is raised while the sink' stop() function is called ([#237](https://github.com/Delgan/loguru/issues/237) <https://github.com/Delgan/loguru/issues/237>_).
• Fix file sink left in an unstable state if an exception occurred during retention or compression process ([#238](https://github.com/Delgan/loguru/issues/238) <https://github.com/Delgan/loguru/issues/238>_).
• Fix situation where changes made to record["message"] were unexpectedly ignored when opt(colors=True), causing "out-of-date" message to be logged due to implementation details ([#221](https://github.com/Delgan/loguru/issues/221) <https://github.com/Delgan/loguru/issues/221>_).
• Fix possible exception if a stream having an isatty() method returning True but not being compatible with colorama is used on Windows ([#249](https://github.com/Delgan/loguru/issues/249) <https://github.com/Delgan/loguru/issues/249>_).
• Fix exceptions occurring in coroutine sinks never retrieved and hence causing warnings ([#227](https://github.com/Delgan/loguru/issues/227) <https://github.com/Delgan/loguru/issues/227>_).

Commits

• f31e971 Bump version to 0.5.3
• 3394fdb Update Changelog to reference #309 fix
• 44f6771 Fix removing simple queue in child processes (#325)
• 296635c Fix possible exception while formatting non-string message (#331)
• b77f4fd Correct simple typo in docs, propogates -> propagates (#323)
• e48f3e4 Bump version to 0.5.2
• d93c19f Flesh out the few remaining incomplete annotations (#316)
• 084dffd Fix tests fails (since pytest upgrade) due to standard logging misuse
• 9a40e58 Fix error with "enqueue=True" and non-picklable exception (#298)
• 6f86f48 Refactor usage of "inspect" functions for simplification
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.