Hallo Helmut,
On 20 April 2018 at 22:01, Helmut Grohne wrote:
| Package: python-rpy
| Version: 1.0.3-30+b3
| Severity: serious
| User: helm...@debian.org
| Usertags: python-import
|
| After installing python-rpy importing the module rpy
| into a python interpreter fails with the following error:
|
| Traceback (most recent call last):
| File "", line 1, in
| File "/usr/lib/python2.7/dist-packages/rpy.py", line 134, in
| """ % RVERSION)
| RuntimeError: No module named _rpy3044
|
| RPy module can not be imported. Please check if your rpy
| installation supports R 3.4.4. If you have multiple R versions
| installed, you may need to set RHOME before importing rpy. For
| example:
|
| >>> from rpy_options import set_options
| >>> set_options(RHOME='c:/progra~1/r/rw2011/')
| >>> from rpy import *
|
|
|
| The vast majority of import failures is attributed to missing dependencies.
| Often times that manifests as an ImportError or ModuleNotFoundError.
| Typically, dependencies should be inserted by dh-python via ${python:Depends}
| or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
| install_requires in setup.py. Sometimes a missing dependency of a dependency
| is the cause, in such cases this bug should be reassigned.
rpy was abandonded upstream maybe a decade ago, maybe longer. It needs hard
rebuilds for each new R version -- here R 3.4.4 -- and at some point that
just ceased to be useful.
There is rpy2 which is current and maintained for python 3. We also forked
off the last version of rpy2 that can be build with python 2.7 as another
software suite needed that.
Please switch to rpy2.
Dirk
|
| Helmut
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org