You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
use logging module/file instead of any prints like in ddlpy (including logging level and set globally how hatyan should print nothing, or to screen, or tot file)
enable verbose in cli
add silent mode?
check logging from cli (initialization/finalization and exec print in console or in STDOUT.txt, depending on users wishes)
check acceptance tests (do not timeout with new logging?) >> spatial_plot and numbering_extremes have timeout
predictie_2022_frommergedcomp_LAT has no decent error message in pytest anymore
overwrite instead of unique-outputdir argument
clean up cli function
disable matplotlib logging in case of verbose cli or debug logging level in spyder/jupyter: "DEBUG:matplotlib.font_manager:findfont: score(FontEntry(fname='C:\\Windows\\Fonts\\LTYPE.TTF', name='Lucida Sans Typewriter', style='normal', variant='normal', weight=400, stretch='normal', size='scalable')) = 10.05" >> maybe set more things as info and test if warning level suppresses these. In that case it does not have to be solved.
"DEBUG:matplotlib.font_manager:findfont: score(FontEntry(fname='C:\\Windows\\Fonts\\LTYPE.TTF', name='Lucida Sans Typewriter', style='normal', variant='normal', weight=400, stretch='normal', size='scalable')) = 10.05"
>> maybe set more things as info and test if warning level suppresses these. In that case it does not have to be solved.name
? >> no_read_components_analysis_settings
#177add debug in example notebook:
merge debug lines into one:
The text was updated successfully, but these errors were encountered: