> The one failed tests is a forced failure, and a visual inspection is > hopefully informative enough. > > self.assertTrue(False) # arrays of unicode characters causing segfault > > self.assertTrue(False): "assert that False is True"; this is the signature > of forced failed test. This is followed by a comment about why this test is > failing, as this is an alternative to a segfault that would prevent going > any further with the tests. >
OK. But I still have no idea why arrays of unicode characters are causing segfault, and apparently no one on the list does either since no one has actually offered anything in the way of constructive help. So no - I'd say a visual inspection (at least for me) is not informative enough. >> Anyone have any ideas, before I ditch rpy2 and revert to good-old rpy? >> > > That's an idea. Since you are with R-2.9, at least this should not translate > into an other email like: > "I cannot seem to use rpy with R-2.10. Anyone have any ideas, before I ditch > rpy and go for the brand-new rpy2 ?" I don't really understand this flippant comment. Is this not the right place to ask people for help about this? As far as I can tell, I ran a standard install that worked without giving any errors, and then one of the standard tests failed with a mildly incomprehensible error. This seems to be a sensible thing to ask for help about. With no help forthcoming I have reverted to rpy for the moment so that the older code I have written actually works. It would be nice to migrate it all to rpy2 - but I'll obviously need a working install of rpy2 before that. ;-) Nick ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ rpy-list mailing list rpy-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rpy-list
