-
Notifications
You must be signed in to change notification settings - Fork 3
logwrap breaks functions #35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Debugging... |
Thank you for quick response! All mentioned libraries you can find at PyPI. Decorated function is GeoVector.get_shape from telluric library. Should I provide anything else? |
No, I found place:
I'll make validation safer on logwrap side, but this error means, that |
Expect fix on evening |
(#36) Fix legacy Signed-off-by: Alexey Stepanov <[email protected]>
Done and released 4.0.2/5.0.1: Test output at log:
|
Thank you very much, Alexey! I have one questions related to the library. Now it is not possible to bypass |
No, logwrap just log function call to debug (if not verbose, else info),
call function and lor result/crash. No any changes to function and result
produced, logger is not re-configured (so if log_level is warning, for
example, in logs will be only crash info). If logger is not configured -
logwrap not produce any side-effects (except small time lag during data
processing and send to logger)
вт, 14 авг. 2018 г., 21:09 Denis Rykov <[email protected]>:
… Thank you very much, Alexey!
I have one questions related to the library. Now it is not possible to
bypass logwrap if current log level is higher then log_level, right? It
would be handy if logwrap decorator be able to return original function
in this case.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APSmM52ZbFCy95_G57eJ0ahLgloF6Xw_ks5uQyCFgaJpZM4V76mn>
.
|
Using
logwrap
breaks functions. When I add@logwrap.logwrap
toget_shape
function it stops working:Without
@logwrap.logwrap
all works as expected.The text was updated successfully, but these errors were encountered: