This PR contains the following updates:
Release Notes
Delgan/loguru
Compare Source
=====================
- 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>
_).
- 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>
_).
- 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>
_).
Compare Source
=====================
- 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>
_).
- 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>
_).
- 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>
_).
- 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>
_).
- 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>
_).
- Fix possible deadlocks on Linux when
multiprocessing.Process()
collides with enqueue=True
or threading
(#​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>
_).
- 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>
_).
- 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>
_).
- 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>
_).
- 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>
_).
- 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>
_).
- Fix exceptions occurring in coroutine sinks never retrieved and hence causing warnings (
#​227 <https://github.com/Delgan/loguru/issues/227>
_).
Renovate configuration
📅 Schedule: 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.
This PR contains the following updates:
==0.4.1
->==0.5.1
Release Notes
Delgan/loguru
v0.5.1
Compare Source
=====================
extra
dict is used byLogRecord
in order to prevent possibleKeyError
with standardlogging
handlers (#​271 <https://github.com/Delgan/loguru/issues/271>
_).default
optional argument tologger.catch()
, it should be the returned value by the decorated function in case an error occurred (#​272 <https://github.com/Delgan/loguru/issues/272>
_).ValueError
when usingserialize=True
in combination withlogger.catch()
orlogger.opt(record=True)
due to circular reference of therecord
dict (#​286 <https://github.com/Delgan/loguru/issues/286>
_).v0.5.0
Compare Source
=====================
no
of levels once they have been added in order to prevent surprising behavior (#​209 <https://github.com/Delgan/loguru/issues/209>
_).**kwargs
to theextra
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>
_).onerror
optional argument tologger.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>
_).exclude
optional argument tologger.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>
_).complete()
to make it callable from non-asynchronous functions, it can thus be used ifenqueue=True
to make sure all messages have been processed (#​231 <https://github.com/Delgan/loguru/issues/231>
_).multiprocessing.Process()
collides withenqueue=True
orthreading
(#​231 <https://github.com/Delgan/loguru/issues/231>
_).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>
_).retention
being too restrictive, it now matches files based on the pattern"basename(.*).ext(.*)"
(#​229 <https://github.com/Delgan/loguru/issues/229>
_).remove()
a handler if an exception is raised while the sink'stop()
function is called (#​237 <https://github.com/Delgan/loguru/issues/237>
_).retention
orcompression
process (#​238 <https://github.com/Delgan/loguru/issues/238>
_).record["message"]
were unexpectedly ignored whenopt(colors=True)
, causing "out-of-date"message
to be logged due to implementation details (#​221 <https://github.com/Delgan/loguru/issues/221>
_).isatty()
method returningTrue
but not being compatible withcolorama
is used on Windows (#​249 <https://github.com/Delgan/loguru/issues/249>
_).#​227 <https://github.com/Delgan/loguru/issues/227>
_).Renovate configuration
📅 Schedule: 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.