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
@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?