# Rpy2 pip installation fails

**URL:** <https://discourse.slicer.org/t/rpy2-pip-installation-fails/4883>\
**Category:** Support\
**Created:** [November 27, 2018, 6:03am UTC](https://discourse.slicer.org/t/rpy2-pip-installation-fails/4883 "2018-11-27T06:03:30Z")\
**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:** [November 27, 2018, 6:58am UTC](https://discourse.slicer.org/t/rpy2-pip-installation-fails/4883/3 "2018-11-27T06:58:54Z")

</div>

Yes, from briefly looking at the Rpy2 documentation there are some precompiled binaries. If you’re using Windows, you’re not going to be able to use this package in Slicer’s environment at this time. I recommend using pure python packages when using Slicer on Windows.

From the other thread that you linked above, the important information is in JC’s [comment](https://discourse.slicer.org/t/slicer-python-packages-use-and-install/984/2).

> Second, on linux (and most likely macOS), it is indeed **possible to pip install official packages** (even the including binaries like `scipy` , `tensorflow` , …).
> 
> On windows, it will currently work only for _pure_ python wheels because the official package for python 2.7 are built with a compiler than the one used for the official wheels. Note that this will change as soon as we standardize on Visual Studio 2015 and switch to python \>= 3.5.

The work towards python3 I believe is scheduled following a 4.10.1 release. So likely early next year.

---

_[View the full topic](https://discourse.slicer.org/t/rpy2-pip-installation-fails/4883)._