Until now, the Python console only displayed Python outputs and Python log messages. Therefore, if a Python command executed a VTK method and that VTK method logged an error or warning, it was not immediately visible for the developer (the developer had to notice the change in the log icon, click on…

It’s great to see log messages from VTK in the python console as you show in your images above! @lassoan Is this change supposed to impact the functionality that is the Slicer_BUILD_WIN32_CONSOLE_LAUNCHER option with local Slicer builds? With that option on Windows we would see a console window ope…

[image] jamesobutler: Currently with the latest Slicer preview, modules that have any python logging do not display these messages to the Win32 console window Previously, Slicer relied on standard output for Python logging (the Python logger printed on the standard output and the application …

With these latest changes, is there any value to still have Slicer_BUILD_WIN32_CONSOLE_LAUNCHER as a a default build option if building Python support is a default option which supports viewing all the output on the python console? I’m thinking about some new python Slicer developers that may get co…

For typing Python commands or debugging Python code I would recommend using the Python console. For checking what happened in the application, the application log viewer has the slight advantages (filtering, grouping, and clearing) compared to the Python console. For reporting errors, the Help/Rep…

Is there a way to set the Python log level from Python? I looked in slicer.app and didn’t find anything obvious. I have some code that intentionally calls methods that trigger warnings/errors to probe/test a configuration and would like to temporarily disable the logs. Something like: oldLevel =…

You can set the Python log level from the Slicer settings: [image] Using code, slicer.app contains slicer.app.setPythonConsoleLogLevel() which you can use such as slicer.app.setPythonConsoleLogLevel(ctk.ctkErrorLogLevel.Error) to set it to the Error level. Unfortunately it appears that the None le…

Log level in the Python console is a user preference. Modules can of course can change it, but doing so would upset users. If you want to change the level to avoid excessive amount of error/warning messages then I would recommend to fix the root cause of those. [image] jamesobutler: ctk.ctkErro…

How about any of the following ideas? ctk.ctkErrorLogLevel.Null ctk.ctkErrorLogLevel.NoneLog ctk.ctkErrorLogLevel.NoLog ctk.ctkErrorLogLevel.Off ctk.ctkErrorLogLevel.Silent

Off sounds good to me. We could deprecate None but keep it around for a while for backward compatibility.

I agree that module shouldn’t change user preferences. In my case, I’m trying to run some unit tests that will intentionally trigger some warnings and errors while testing the returned values. At that point, all the tests succeed but the user will see multiple errors and warnings. To avoid this c…

New feature: Python console displays more log messages

Development

Topic		Replies	Views
Info level logging messages do not appear in Python console Development python	5	6004	November 15, 2023
Large discrepancy in logged output in Python vs. Bash Consoles Support python	5	99	July 22, 2025
Logging with a python script Support python	0	90	June 12, 2024
How can I redirect std::cout to Python Interactor? Development	2	298	December 13, 2023
How to disable automatic logging into the Python Interactor? Development python	5	1303	October 28, 2022

New feature: Python console displays more log messages

Related topics