TrafficToll
TrafficToll copied to clipboard
Bump loguru from 0.4.1 to 0.5.3
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=Truewith third party library likeuwsgi(#309, thanks@dstlmrk).- Fix possible exception during formatting of non-string messages (#331).
0.5.2
- Fix
AttributeErrorwithin handlers usingserialize=Truewhen callinglogger.exception()outside of the context of an exception (#296).- Fix error while logging an exception containing a non-picklable
valueto a handler withenqueue=True(#298).- Add support for async callable classes (with
__call__method) used as sinks (#294, thanks@jessekrubin).0.5.1
- Modify the way the
extradict is used byLogRecordin order to prevent possibleKeyErrorwith standardlogginghandlers (#271).- Add a new
defaultoptional argument tologger.catch(), it should be the returned value by the decorated function in case an error occurred (#272).- Fix
ValueErrorwhen usingserialize=Truein combination withlogger.catch()orlogger.opt(record=True)due to circular reference of therecorddict (#286).0.5.0
- Remove the possibility to modify the severity
noof levels once they have been added in order to prevent surprising behavior (#209).- Add better support for "structured logging" by automatically adding
**kwargsto theextradict 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
onerroroptional argument tologger.catch(), it should be a function which will be called when an exception occurs in order to customize error handling (#224).- Add a new
excludeoptional argument tologger.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 ifenqueue=Trueto make sure all messages have been processed (#231).- Fix possible deadlocks on Linux when
multiprocessing.Process()collides withenqueue=Trueorthreading(#231).- Fix
compressionfunction 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
retentionbeing 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
retentionorcompressionprocess (#238).- Fix situation where changes made to
record["message"]were unexpectedly ignored whenopt(colors=True), causing "out-of-date"messageto be logged due to implementation details (#221).- Fix possible exception if a stream having an
isatty()method returningTruebut not being compatible withcoloramais 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=Truewith third party library likeuwsgi([#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
AttributeErrorwithin handlers usingserialize=Truewhen callinglogger.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
valueto a handler withenqueue=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
extradict is used byLogRecordin order to prevent possibleKeyErrorwith standardlogginghandlers ([#271](https://github.com/Delgan/loguru/issues/271) <https://github.com/Delgan/loguru/issues/271>_).- Add a new
defaultoptional 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) <https://github.com/Delgan/loguru/issues/272>_).- Fix
ValueErrorwhen usingserialize=Truein combination withlogger.catch()orlogger.opt(record=True)due to circular reference of therecorddict ([#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
noof 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
**kwargsto theextradict 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
onerroroptional 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) <https://github.com/Delgan/loguru/issues/224>_).- Add a new
excludeoptional 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) <https://github.com/Delgan/loguru/issues/248>_).- Modify
complete()to make it callable from non-asynchronous functions, it can thus be used ifenqueue=Trueto 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 withenqueue=Trueorthreading([#231](https://github.com/Delgan/loguru/issues/231) <https://github.com/Delgan/loguru/issues/231>_).- Fix
compressionfunction 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
retentionbeing 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
retentionorcompressionprocess ([#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 whenopt(colors=True), causing "out-of-date"messageto 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 returningTruebut not being compatible withcoloramais 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
f31e971Bump version to 0.5.33394fdbUpdate Changelog to reference #309 fix44f6771Fix removing simple queue in child processes (#325)296635cFix possible exception while formatting non-string message (#331)b77f4fdCorrect simple typo in docs, propogates -> propagates (#323)e48f3e4Bump version to 0.5.2d93c19fFlesh out the few remaining incomplete annotations (#316)084dffdFix tests fails (since pytest upgrade) due to standard logging misuse9a40e58Fix error with "enqueue=True" and non-picklable exception (#298)6f86f48Refactor 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.