# Printing in Python CLI modules

**URL:** https://discourse.slicer.org/t/printing-in-python-cli-modules/29516
**Category:** Development
**Created:** [May 17, 2023, 4:53pm UTC](https://discourse.slicer.org/t/printing-in-python-cli-modules/29516 "2023-05-17T16:53:25Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![benzwick](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/benzwick/32/80521_2.png) [@benzwick](https://discourse.slicer.org/u/benzwick)
#### Post date: [May 17, 2023, 5:30pm UTC](https://discourse.slicer.org/t/printing-in-python-cli-modules/29516/3 "2023-05-17T17:30:03Z")

</div>

I’m developing an [extension](https://github.com/SlicerCBM/SlicerFreeSurferCommands) to run some FreeSurfer commands inside Slicer. Python CLI modules seem perfect because all I need is a GUI for running existing external commands. So far I have the SynthStrip command implemented and it works very well. The only issue is there is no way to know what is happening while the module is running, which for some commands might take several minutes or longer. As far as I understand, a scripted module would [block the GUI](https://discourse.slicer.org/t/basic-questions-on-cli-modules-vs-scripted-modules/10782/2), which would not be a good trade-off I think.

---

_[View the full topic](https://discourse.slicer.org/t/printing-in-python-cli-modules/29516)._