# Slicer-Python Packages Use and Install

**URL:** https://discourse.slicer.org/t/slicer-python-packages-use-and-install/984
**Category:** Support
**Created:** [August 31, 2017, 9:27pm UTC](https://discourse.slicer.org/t/slicer-python-packages-use-and-install/984 "2017-08-31T21:27:14Z")
**Posts on this page:** 1
**Showing post:** 31

<div class="post-metadata">

### Author: ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [October 25, 2018, 4:20am UTC](https://discourse.slicer.org/t/slicer-python-packages-use-and-install/984/31 "2018-10-25T04:20:11Z")

</div>

A simpler example is PyCLIModule4Test example:

- Module parameters/GUI specification: [https://github.com/Slicer/Slicer/blob/master/Base/QTCLI/Testing/PyCLIModule4Test.xml](https://github.com/Slicer/Slicer/blob/master/Base/QTCLI/Testing/PyCLIModule4Test.xml)
- Executed python script:  
[https://github.com/Slicer/Slicer/blob/master/Base/QTCLI/Testing/PyCLIModule4Test.py](https://github.com/Slicer/Slicer/blob/master/Base/QTCLI/Testing/PyCLIModule4Test.py)

In the executed Python script you can launch an external Python interpreter (Python3, anaconda, etc.), similarly to how it is done here: [Subprocess call in Python interpreter results in memory corruption](https://discourse.slicer.org/t/subprocess-call-in-python-interpreter-results-in-memory-corruption/919/11?u=lassoan)

---

_[View the full topic](https://discourse.slicer.org/t/slicer-python-packages-use-and-install/984)._