# About release a python extension with a CLI module

**URL:** <https://discourse.slicer.org/t/about-release-a-python-extension-with-a-cli-module/30420>\
**Category:** Development\
**Tags:** python, extensions\
**Created:** [July 5, 2023, 9:49pm UTC](https://discourse.slicer.org/t/about-release-a-python-extension-with-a-cli-module/30420 "2023-07-05T21:49:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bywbilly](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@bywbilly](https://discourse.slicer.org/u/bywbilly)\
**Post date:** [July 5, 2023, 9:49pm UTC](https://discourse.slicer.org/t/about-release-a-python-extension-with-a-cli-module/30420/1 "2023-07-05T21:49:01Z")

</div>

Hi 3D Slicer Community,

We are developing a Python extension and plan to release it into the 3D slicer community. To make the main time-consuming part run in the backend, we create a CLI module following this repo: [GitHub - lassoan/SlicerPythonCLIExample: Example extension for 3D Slicer that demonstrates how to make a Python script available as a CLI module](https://github.com/lassoan/SlicerPythonCLIExample).

I am wondering when we prepare the extension repo in GitHub, what should we do with this Python CLI module?

Thanks!
