Hi,
I am currently engaged developing a plugin, the complexity of which necessitated the integration of logging. While the implementation of logging in C# has been relatively smooth, despite minor leaks due to the logger inadvertently logging Rhino core, the same cannot be said for its implementation in IronPython.
I’ve been leveraging the logging package as detailed in the IronPython 2.7.2b1 documentation. However, I’ve encountered an issue where, post-compilation, the script refuses to execute. This leads me to suspect a potential compatibility issue.
For those who may need to implement logging in IronPython, I would recommend considering the use of the alternative package “traceback”. However the Logging and Traceback packages serve different purposes. Traceback is primarily used for stacktrace reports, while the logging package allows for the definition of custom severity levels, output formats, and log message destinations. The latter is typically employed for system monitoring, error tracking, and debugging during a program’s normal operation.
In essence, it would be great if the logging package worked out of the box.
Interestingly, the logging package operates as expected when used within the Rhino Python IDE. However, once compiled as a plugin, the command can’t be run.
-Farouk