Bump loguru from 0.3.2 to 0.5.3

[dependabot-preview]

Bumps loguru from 0.3.2 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).

0.4.1

• Deprecate the ansi parameter of .opt() in favor of colors which is a name more appropriate.
• Prevent unrelated files and directories to be incorrectly collected thus causing errors during the retention process (#195, thanks @gazpachoking).
• Strip color markups contained in record["message"] when logging with .opt(ansi=True) instead of leaving them as is (#198).
• Ignore color markups contained in *args and **kwargs when logging with .opt(ansi=True), leave them as is instead of trying to use them to colorize the message which could cause undesirable errors (#197).

0.4.0

• Add support for coroutine functions used as sinks and add the new logger.complete() asynchronous method to await them (#171).
• Add a way to filter logs using one level per module in the form of a dict passed to the filter argument (#148).
• Add type hints to annotate the public methods using a .pyi stub file (#162).
• Add support for copy.deepcopy() of the logger allowing multiple independent loggers with separate set of handlers (#72).
• Add the possibility to convert datetime to UTC before formatting (in logs and filenames) by adding "!UTC" at the end of the time format specifier (#128).
• Add the level name as the first argument of namedtuple returned by the .level() method.
• Remove class objects from the list of supported sinks and restrict usage of **kwargs in .add() to file sink only. User is in charge of instantiating sink and wrapping additional keyword arguments if needed, before passing it to the .add() method.
• Rename the logger.configure() keyword argument patch to patcher so it better matches the signature of logger.patch().
• Fix incompatibility with multiprocessing on Windows by entirely refactoring the internal structure of the logger so it can be inherited by child processes along with added handlers (#108).
• Fix AttributeError while using a file sink on some distributions (like Alpine Linux) missing the os.getxattr and os.setxattr functions (#158, thanks @joshgordon).
• Fix values wrongly displayed for keyword arguments during exception formatting with diagnose=True (#144).
• Fix logging messages wrongly chopped off at the end while using standard logging.Handler sinks with .opt(raw=True) (#136).
• Fix potential errors during rotation if destination file exists due to large resolution clock on Windows (#179).

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, thanks @dstlmrk).
• Fix possible exception during formatting of non-string messages (#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).
• 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 (2020-06-12)

• 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 (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).
• 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).

0.4.1 (2020-01-19)

• Deprecate the ansi parameter of .opt() in favor of colors which is a name more appropriate.
• Prevent unrelated files and directories to be incorrectly collected thus causing errors during the retention process (#195, thanks @gazpachoking).
• Strip color markups contained in record["message"] when logging with .opt(ansi=True) instead of leaving them as is (#198).
• Ignore color markups contained in *args and **kwargs when logging with .opt(ansi=True), leave them as is instead of trying to use them to colorize the message which could cause undesirable errors (#197).

0.4.0 (2019-12-02)

• Add support for coroutine functions used as sinks and add the new logger.complete() asynchronous method to await them (#171).
• Add a way to filter logs using one level per module in the form of a dict passed to the filter argument (#148).

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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)