# Is Slicer's Python environment complete?

**URL:** <https://discourse.slicer.org/t/is-slicers-python-environment-complete/18038>\
**Category:** Development\
**Tags:** python\
**Created:** [June 9, 2021, 12:07pm UTC](https://discourse.slicer.org/t/is-slicers-python-environment-complete/18038 "2021-06-09T12:07:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![slicer365](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/slicer365/32/67549_2.png) [@slicer365](https://discourse.slicer.org/u/slicer365)\
**Post date:** [June 9, 2021, 12:07pm UTC](https://discourse.slicer.org/t/is-slicers-python-environment-complete/18038/1 "2021-06-09T12:07:35Z")

</div>

Is the Python in slicer the complete version?

---

<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:** [June 9, 2021, 12:58pm UTC](https://discourse.slicer.org/t/is-slicers-python-environment-complete/18038/2 "2021-06-09T12:58:14Z")

</div>

Yes, Slicer’s Python is complete. We only experienced difference in behavior in parallel processing and asynchronous io. Also, The PythonSlicer. exe interpreter is very basic (just redirection of input and output).