Revision: 415
          http://rpy.svn.sourceforge.net/rpy/?rev=415&view=rev
Author:   lgautier
Date:     2008-03-03 13:32:56 -0800 (Mon, 03 Mar 2008)

Log Message:
-----------
Typo in the test

Modified Paths:
--------------
    trunk/sandbox/rpy_nextgen/rinterface/tests/test_SexpVector.py

Modified: trunk/sandbox/rpy_nextgen/rinterface/tests/test_SexpVector.py
===================================================================
--- trunk/sandbox/rpy_nextgen/rinterface/tests/test_SexpVector.py       
2008-03-03 21:32:15 UTC (rev 414)
+++ trunk/sandbox/rpy_nextgen/rinterface/tests/test_SexpVector.py       
2008-03-03 21:32:56 UTC (rev 415)
@@ -2,7 +2,7 @@
 import rinterface
 
 #FIXME: can starting and stopping an embedded R be done several times ?
-rinterface.initEmbeddedR("foo", "--vanilla", "--no-save")
+rinterface.initEmbeddedR("foo", "--vanilla", "--no-save", "--quiet")
 
 class SexpVectorTestCase(unittest.TestCase):
     #def setUpt(self):
@@ -22,12 +22,12 @@
         seq_R = rinterface.globalEnv.get("seq")
         
         mySeq = seq_R(rinterface.SexpVector([0, ], rinterface.INTSXP),
-                     rinterface.SexpVector([10, ], rinterface.INTSXP))
+                      rinterface.SexpVector([10, ], rinterface.INTSXP))
         
         myList = as_list_R(mySeq)
         
-        for i, li in enumerate(Rlist):
-            self.assertEquals(i, Rlist[i][0])
+        for i, li in enumerate(myList):
+            self.assertEquals(i, myList[i][0])
 
 if __name__ == '__main__':
      unittest.main()


This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
rpy-list mailing list
rpy-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rpy-list

Reply via email to