On Oct 11, 2007, at 3:35 PM, Brian Miles wrote:
On Oct 8, 2007, at 1:01 PM, [EMAIL PROTECTED]
wrote:
Date: Sun, 7 Oct 2007 09:38:16 -0400
From: "Michael Boldin" <[EMAIL PROTECTED]>
Subject: [Rpy] Windows import rpy problems
To:
Message-ID: <[EMAIL PROTECTED]>
Co
2007, at 1:01 PM, [EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]> wrote:
>>> Date: Sun, 7 Oct 2007 09:38:16 -0400
>>>
>>> From: "Michael Boldin" <[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>>
>>>
>>> Subject:
[EMAIL PROTECTED]> wrote:
>
>> Date: Sun, 7 Oct 2007 09:38:16 -0400
>>
>> From: "Michael Boldin" <[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>>
>>
>> Subject: [Rpy] Windows import rpy problems
>>
>> To: > <mailto:rpy-
On Oct 8, 2007, at 1:01 PM, [EMAIL PROTECTED]
wrote:
Date: Sun, 7 Oct 2007 09:38:16 -0400
From: "Michael Boldin" <[EMAIL PROTECTED]>
Subject: [Rpy] Windows import rpy problems
To:
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
Different messages on this list point to the same basic problem-Python and
RPY silently crashes when 'import rpy' is used in a Windows system. This
Windows RPY problem has two quick solutions (based on my experiments):
(1) Use RPY RC2, which is the older release from December 2006. You
mi