-
Notifications
You must be signed in to change notification settings - Fork 7
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
Missing bug fixes from lantz 0.3 #1
Comments
Regarding lantz-monitor. I am not sure if we should keep this within lantz. I have been using Regarding log_output. I am not sure what is the use of this argument. It toggles between showing the type or the value of the argument. We could just log both. |
Regarding log_output. I am reading out a camera with 12mp frames at 1Gbps. I never want to log this very large datastream. |
@vascotenner Makes sense but maybe we should add it as an standard option for all feats/actions Specific proposal:
To resolve:
|
Specific proposal: To resolve:
Feat(log_values=True)
"""
:param log_values: True: Include values of input and output parameters, False: Only include type in log.
""" |
I think we can do this in pimpmyclass with a custom config flag. |
I have pushed an initial implementation to pimpmyclass here If will test it more and if I am happy I will make a new release and use it in lantz. |
install_requires
log_output
argument, but see below)The text was updated successfully, but these errors were encountered: