previous string_handling located datetime and timestamp files have been moved
to the datetime handling folder
Update readme file with more information about currently covered areas
This error can happend if we search for a key and try to make a value compare and the key does not exist.
Perhaps also when they key should return a list
Remove all class vars for vars that are only used in the loader itsef
- entry_split_char
- entry_convert
- entry_set_empty
The self.settings varr was never used, removed
The config file path exists check is moved to the config data loader
The internal _check_settings_abort is now __check_settings_abort to make it private
lock file updates
Changed that we call stop_listener and not _cleanup on exit
Then call _cleanup from the stop listener
We only need that if we have listeners (queue) anyway
Any float number will be rounded, and everything that is any kind of number will be then converted to int and returned
The rest will be converted to string and normal convert is run
array_search name is deprecated
use find_in_array_from_list
- change parameter order
data (search in) comes before search_params list
- created a TypedDict for the array search params dict entry
It now works correct with start and skip_last settings, the method is now called "call_stack"
Also added auto reset if no output (start too hight) and optional stack separator
This Logger class can be used after the main Log class has been setup, eg in workers
inside pool/fork/thread runs
A new parent class holds all the public methods
init Logger class with "get_logger_settings" or with a dictionary Type LoggerInit that has
logger with type logging.Logger as mandatory and optional Queue entry
It now goes recursive, is case insenstivie for keys and mask keys requests
Checks not for equal but for start/end or inside with edge character set
pytests added
When calling log.exception it automatically writes a short message to the console as error
This error message is tagged <=EXCEPTION> and contains only the message without the stack trace
Settings loader: all errors are thrown where the error happens and not in the print function
The print function if to log will add +1 to the stack level so the error is shown
In the log class in the log wrapper calls add +1 to the stack level to have the error line in the correct place
-> this fixes the stack trace part for now but we still want to have an auto full stack trace simple added
