Thank you for your interest on this problem !
I am sorry I do not remember which version of R was installed on my old
computer. And I do not have access to it anymore..
Have a good week-end !
Aurélie
laurent a écrit :
On Fri, 2008-11-14 at 11:29 -0500, laurent oget wrote:
As i suspected t
On Fri, 2008-11-14 at 11:29 -0500, laurent oget wrote:
> As i suspected there is code to deal with the locale in the main.c of
> R, which switches some locale to "" which means they will use this
> machine's custom locale instead of "C", but they explicitely do not do
> it for LC_NUMERIC
>
> I s
As i suspected there is code to deal with the locale in the main.c of
R, which switches some locale to "" which means they will use this
machine's custom locale instead of "C", but they explicitely do not do
it for LC_NUMERIC
I suspect a
setlocale(LC_NUMERIC,"C") before loading the R library woul
Hello,
With these lines before importing rpy, everything goes perfectly well !
import locale
locale.setlocale(locale.LC_ALL,'C')
Thank you very much for your help Laurent, Barry and Peter !
This fix will help me a lot !
Aurélie
laurent oget a écrit :
Yup, this definitely is broken...
So
I suspect there is a setlocale(LC_ALL,'C') somewhere in the main of R,
but not in the shared library which rpy loads.
Laurent
2008/11/13 Barry Rowlingson <[EMAIL PROTECTED]>:
> 2008/11/13 Aurelie Bornot <[EMAIL PROTECTED]>:
>> Ok
>> So I tried the same chart in python/rpy and in R.
>>
>> Here are
Yup, this definitely is broken...
Somehow in the Rpy version of the postscript file the numbers use , instead of .
I suspect the problem is linked to the locale, i.e. you are using a
french version of the operating system, and in french when you print a
decimal number you should use , instead of
2008/11/13 Aurelie Bornot <[EMAIL PROTECTED]>:
> Ok
> So I tried the same chart in python/rpy and in R.
>
> Here are the lines I type in python/rpy :
> m = pylab.load("test.data")
> m
> array([[ 1., 2.],
>[ 2., 3.],
>[ 3., 4.],
>[ 4., 5.],
>[ 5., 6.],
Ok
So I tried the same chart in python/rpy and in R.
Here are the lines I type in python/rpy :
m = pylab.load("test.data")
m
array([[ 1., 2.],
[ 2., 3.],
[ 3., 4.],
[ 4., 5.],
[ 5., 6.],
[ 6., 7.],
[ 7., 8.],
[ 8., 9.],
[ 9.
I would try to generate the same chart in rpy and directly in R and
compare the postscript files. This would give you, and us, an idea of
what went wrong.
Laurent
2008/11/13 Aurelie Bornot <[EMAIL PROTECTED]>:
> Hello Peter,
>
> Thanks for your answer.
> Yes I have tried this in R itself. And eve
Hello Peter,
Thanks for your answer.
Yes I have tried this in R itself. And everything is OK. It seems that
it is an rpy problem.
Aurélie
Peter a écrit :
On Thu, Nov 13, 2008 at 3:56 PM, Aurelie Bornot
<[EMAIL PROTECTED]> wrote:
Hello everyone,
I used to create postscripts with rpy with
On Thu, Nov 13, 2008 at 3:56 PM, Aurelie Bornot
<[EMAIL PROTECTED]> wrote:
>
> Hello everyone,
>
> I used to create postscripts with rpy without any problem on my old
> computer. This computer was on fedora 7 with python 2.5.1.
> I was given a new computer with fedora 9, python 2.5.1 and 2.8.0, and
Hello everyone,
I used to create postscripts with rpy without any problem on my old
computer. This computer was on fedora 7 with python 2.5.1.
I was given a new computer with fedora 9, python 2.5.1 and 2.8.0, and
now, all my 'old' scripts for making postscripts or pdf do not work
anymore...
Here i
12 matches
Mail list logo