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
During the process of integrating this great implementation on my simulation software I realized that the SC class will log directly to logging.
For those that would like to import the module and use it as-is (my case), it would be great that the exceptions are propagated without logging involved. In this way I would be able to handle and print what is necessary on my software.
At the moment, when the Sim is not running, the class will spam my software logging console with unwanted messages.
Suggestion:
I would suggest to add a verbose flag as part of the class init, which will enable any logging information. You can make it True by default, but at least I get some control :)
Thank you for your answer!
I would rather wait for the proper fix. I use logger across my application, hence I don't want to modify the logging level.
Looking forward to your fix!
During the process of integrating this great implementation on my simulation software I realized that the SC class will log directly to logging.
For those that would like to import the module and use it as-is (my case), it would be great that the exceptions are propagated without logging involved. In this way I would be able to handle and print what is necessary on my software.
At the moment, when the Sim is not running, the class will spam my software logging console with unwanted messages.
Suggestion:
I would suggest to add a verbose flag as part of the class init, which will enable any logging information. You can make it True by default, but at least I get some control :)
Thank you very much in advance!
The text was updated successfully, but these errors were encountered: