# Did sitkUtils.PullVolumeFromSlicer() break with Slicer 5.2?

**URL:** <https://discourse.slicer.org/t/did-sitkutils-pullvolumefromslicer-break-with-slicer-5-2/26863>\
**Category:** Development\
**Created:** [December 21, 2022, 12:36am UTC](https://discourse.slicer.org/t/did-sitkutils-pullvolumefromslicer-break-with-slicer-5-2/26863 "2022-12-21T00:36:09Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [February 7, 2023, 2:00pm UTC](https://discourse.slicer.org/t/did-sitkutils-pullvolumefromslicer-break-with-slicer-5-2/26863/11 "2023-02-07T14:00:50Z")

</div>

Yet another case of a Python package requiring a very specific SimpleITK version has come up - see [Run a Python script as subprocess from Slicer - #12 by lassoan](https://discourse.slicer.org/t/run-a-python-script-as-subprocess-from-slicer/22668/12)

@jcfr is there a solution for this? There are a number of bad-behaving Python packages out there that require a certain SimpleITK version. Should we drop the special Slicer memory image IO to make Slicer compatible with a broader range of SimpleITK versions?

---

_[View the full topic](https://discourse.slicer.org/t/did-sitkutils-pullvolumefromslicer-break-with-slicer-5-2/26863)._