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
To use the Python 'logging' package to write logs is good.
BUT it is BETTER (and simple) to use a dedicated namespace, for example "castle.algorithm.<algo_name>" for the algorithms, and "castle.general" or similar names for the generic parts of the code, and NOT the 'root' namespace.
This because if the library is used in a more complex application, it permits to decide which logs to select.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion! The logging is a bit disorganized right now and could use a look-over to consistently use getLogger(__name__) or similar, and follow the same format everywhere.
Let us know if you are interested in making a PR for this issue!
To use the Python 'logging' package to write logs is good.
BUT it is BETTER (and simple) to use a dedicated namespace, for example "castle.algorithm.<algo_name>" for the algorithms, and "castle.general" or similar names for the generic parts of the code, and NOT the 'root' namespace.
This because if the library is used in a more complex application, it permits to decide which logs to select.
The text was updated successfully, but these errors were encountered: