# Strategies for Distributing Python Programs Securely

**URL:** <https://discourse.slicer.org/t/strategies-for-distributing-python-programs-securely/35807>\
**Category:** Development\
**Created:** [April 29, 2024, 3:44pm UTC](https://discourse.slicer.org/t/strategies-for-distributing-python-programs-securely/35807 "2024-04-29T15:44:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [April 29, 2024, 10:50pm UTC](https://discourse.slicer.org/t/strategies-for-distributing-python-programs-securely/35807/2 "2024-04-29T22:50:09Z")

</div>

I tried the chatbot on this question and I think the answer is a good summary (do others agree?).

> [@Semantic search for this forum](https://discourse.slicer.org/t/semantic-search-for-this-forum/34811/7):
>
> Here’s what the chatbot said in response to this question: [claude\_3\_opus\_bot](https://discourse.slicer.org/u/claude_3_opus_bot)Forum Helper [1m](https://discourse.slicer.org/t/untitled-ai-bot-pm/35822/2) Search Based on my search of the Slicer forum, it looks like converting .py files to .pyc files is still a reasonable approach for distributing Slicer extensions while hiding the original Python source code: [How to hide the code of the script module?](https://discourse.slicer.org/t/how-to-hide-the-code-of-the-script-module/26135/13) In that post from early 2024, it was suggested to write a short Python script that compiles your .py files to .pyc and then replaces the .py files wi…

---

_[View the full topic](https://discourse.slicer.org/t/strategies-for-distributing-python-programs-securely/35807)._