Update dependency loguru to v0.6.0 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
loguru (changelog)	==0.4.1 -> ==0.6.0

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

Delgan/loguru

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

v0.5.3

Compare Source

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

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

v0.5.2

Compare Source

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

• Fix AttributeError within handlers using serialize=True when calling logger.exception() outside of the context of an exception (#&#8203;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 (#&#8203;298 <https://github.com/Delgan/loguru/issues/298>_).
• Add support for async callable classes (with __call__ method) used as sinks (#&#8203;294 <https://github.com/Delgan/loguru/pull/294>, thanks @jessekrubin <https://github.com/jessekrubin>).

v0.5.1

Compare Source

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

• Modify the way the extra dict is used by LogRecord in order to prevent possible KeyError with standard logging handlers (#&#8203;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 (#&#8203;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 (#&#8203;286 <https://github.com/Delgan/loguru/issues/286>_).

v0.5.0

Compare Source

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

• Remove the possibility to modify the severity no of levels once they have been added in order to prevent surprising behavior (#&#8203;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 (#&#8203;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 (#&#8203;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 (#&#8203;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 (#&#8203;231 <https://github.com/Delgan/loguru/issues/231>_).
• Fix possible deadlocks on Linux when multiprocessing.Process() collides with enqueue=True or threading (#&#8203;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 (#&#8203;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(.*)" (#&#8203;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 (#&#8203;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 (#&#8203;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 (#&#8203;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 (#&#8203;249 <https://github.com/Delgan/loguru/issues/249>_).
• Fix exceptions occurring in coroutine sinks never retrieved and hence causing warnings (#&#8203;227 <https://github.com/Delgan/loguru/issues/227>_).

---

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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.