Re: [Rpy] future of rpy 1.0

2008-12-02 Thread Mario Beauchamp
Hi, On Tue, Dec 2, 2008 at 5:38 AM, Peter <[EMAIL PROTECTED]> wrote: > > When building python extensions, you are generally recommended to use > the same compiler as was used for python. On Windows with the > official Python 2.3, this meant MSVC 6.0, but for later versions of > Python more recent

Re: [Rpy] RPy2 fails on Windows and R-2.8.0

2008-12-02 Thread Laurent Gautier
Peter wrote: > On Tue, Dec 2, 2008 at 11:50 AM, Marcos Silva <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I made the changes suggested. >> >> - I created a R_HOME variable in windows with value "C:\Program >> Files\R\R-2.8.0" >> - "import win32api" is OK in my Python installation >> >> From R I get:

Re: [Rpy] Cannot build rpy 1.0.3 under windows using Visual C++.

2008-12-02 Thread laurent oget
Doing it with mingw does work (I did it yesterday). If playing with obsolete microsoft tools is your idea fo fun you have two ways of getting R.lib: - Build R from source - follow http://support.microsoft.com/kb/131313 Laurent 2008/12/2 Bo Peng <[EMAIL PROTECTED]>: > When I do 'python setup.py i

[Rpy] Cannot build rpy 1.0.3 under windows using Visual C++.

2008-12-02 Thread Bo Peng
When I do 'python setup.py install', everything compiles well but the last link command failed with 'R.lib' not found. Am I supposed to use mingw, or convert R.dll to R.lib in advance? Thanks. Bo - This SF.Net email is sponso

Re: [Rpy] RPy2 fails on Windows and R-2.8.0

2008-12-02 Thread Peter
On Tue, Dec 2, 2008 at 11:50 AM, Marcos Silva <[EMAIL PROTECTED]> wrote: > Hi, > > I made the changes suggested. > > - I created a R_HOME variable in windows with value "C:\Program > Files\R\R-2.8.0" > - "import win32api" is OK in my Python installation > > From R I get: > >> Sys.getenv("R_HOME

[Rpy] SF.net SVN: rpy:[709] trunk/rpy/debian

2008-12-02 Thread eddelbuettel
Revision: 709 http://rpy.svn.sourceforge.net/rpy/?rev=709&view=rev Author: eddelbuettel Date: 2008-12-02 11:13:34 + (Tue, 02 Dec 2008) Log Message: --- synced debian/ to most recent package release Modified Paths: -- trunk/rpy/debian/changelog trunk

Re: [Rpy] RPy2 fails on Windows and R-2.8.0

2008-12-02 Thread Marcos Silva
Hi, I made the changes suggested. - I created a R_HOME variable in windows with value "C:\Program Files\R\R-2.8.0" - "import win32api" is OK in my Python installation >From R I get: > Sys.getenv("R_HOME") R_HOME "C:\\PROGRA~1\\R\\R-28~1.0" > R.home() [1] "C:\\PROGRA~1\

Re: [Rpy] future of rpy 1.0

2008-12-02 Thread Peter
>>> Its been a while but I have built rpy on Windows with Python 2.3 and >>> MSCV 6.0 (the compiler used for the official Python 2.3 installation). >> >> So it is possible then? I use the msvc toolkit (same compiler) to >> build my extensions so if I could do the same with rpy, I would be >> less d

Re: [Rpy] RPy2 fails on Windows and R-2.8.0

2008-12-02 Thread Peter
Marcos wrote: >> The responses to your questions are: >> >> 1. No, I did not setup R_HOME. By the way, how can I do this? >> Laurent wrote: > > set R_HOME=C:\Program Files\R\R-2.8.0 should fix this. It looks like > your R_HOME variable is set, but set to a wrong value. > If you were asking how to

Re: [Rpy] future of rpy 1.0

2008-12-02 Thread Laurent Gautier
Mario Beauchamp wrote: > Hi, > > On Mon, Dec 1, 2008 at 5:30 AM, Peter <[EMAIL PROTECTED]> wrote: >> Hopefully the backward compatibility interface in rpy 2.0 will >> eventually make upgrading from rpy1 to rpy2 simple. > > I will eventually make the upgrade but since rpy is bundled into my > soft

Re: [Rpy] future of rpy 1.0

2008-12-02 Thread Laurent Gautier
Mario Beauchamp wrote: > Hi Greg, > > On Mon, Dec 1, 2008 at 10:39 AM, Warnes, Gregory R. > <[EMAIL PROTECTED]> wrote: >> RPy 1.0 will continue to exist, and bug fixes will be made, but feature >> enhancements will occur in RPy2 > > Fair enough. > >> I'll try to create a Windows installer for 2.