Created attachment 332962 [details] build log On my hardened ~amd64 machine with gcc-4.7.2 I see the following test failure for rpy: === FAIL: testInterruptR (rpy2.rinterface.tests.test_EmbeddedR.EmbeddedRTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/tmp/portage/dev-python/rpy-2.2.6-r1/work/rpy2-2.2.6/build-2.7/lib.linux-x86_64-2.7/rpy2/rinterface/tests/test_EmbeddedR.py", line 171, in testInterruptR self.assertFalse(ret_code is None) # Interruption failed AssertionError: True is not false ===
Created attachment 332964 [details] emerge --info
I get some test failures but not in py2.7 but py3. However, they're issue tracker maker @ https://sourceforge.net/p/rpy/bugs/ is absent of any way of making a new issue.
@idella4: The issue tracker for rpy2 is on bitbucket. https://bitbucket.org/lgautier/rpy2/issues/
right. this relates to 2.2.6-r1. On my machine, it passes py2.7, however the kernel is not hardened and gcc is 4.6.3. According to the package author; "Python 3.2 is not tested (by myself), only Python 3.3. Numpy was not tested under Python 3 because it did not build for me." which rather makes a mockery of the ebuild's RESTRICT_PYTHON_ABIS="2.5 *-jython 2.7-pypy-*" leaving open slather for py3. rpy-2.3.1 was added to the tree first week of new year. Without a second tester to match your system's kernel and gcc, combined with the above, I don't see much value in this bug, except to prompt to restrict py3 consequent to test-restrict-python-abis being now dropped.
rpy-2.3.8 passes this test for me, so I'm closing this bug.
