# Couldn't find SlicerRadiomics

**URL:** <https://discourse.slicer.org/t/couldnt-find-slicerradiomics/22361>\
**Category:** Support\
**Created:** [March 8, 2022, 5:32am UTC](https://discourse.slicer.org/t/couldnt-find-slicerradiomics/22361 "2022-03-08T05:32:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [March 8, 2022, 10:07pm UTC](https://discourse.slicer.org/t/couldnt-find-slicerradiomics/22361/3 "2022-03-08T22:07:13Z")

</div>

The specifics of the issue are found at the linked thread below. Currently, the issue hasn’t been looked into further.

> [@Factory build of python extensions conflicting with each other](https://discourse.slicer.org/t/factory-build-of-python-extensions-conflicting-with-each-other/21935):
>
> I noticed an issue occurring during the factory build of python extensions where an extension may be installing new python packages which results in Slicer core python packages having their installed version modified. This may be with general tools like pip, setuptools, etc. When this happens if impacts all extensions built afterwards which have to use modified versions of these packages. This makes it difficult to make sure a Slicer extension that includes additional python packages is going t…

---

_[View the full topic](https://discourse.slicer.org/t/couldnt-find-slicerradiomics/22361)._