On May 21, 5:08 pm, Maciek Sykulski wrote:
> The old patch somewhat
> works.http://trac.sagemath.org/sage_trac/attachment/ticket/11436/trac_11436...
>
> It didn't apply automatically because the source in sage-5.0
> looks a bit different now:
> -
> def _read_in_file_command(self, fi
The old patch somewhat works.
http://trac.sagemath.org/sage_trac/attachment/ticket/11436/trac_11436.patch
It didn't apply automatically because the source in sage-5.0
looks a bit different now:
-
def _read_in_file_command(self, filename):
r"""
Return the R command (as a
On May 20, 5:38 pm, Maciek Sykulski wrote:
> Thanks Nils.
> It turns out the problem concerns any text output from R, not only
> error messages.
> In each case R code is being evaluated (ex. values of variables
> change),
> however no sign of feedback from R if the input is too long.
>
> sage: R
On May 20, 5:38 pm, Maciek Sykulski wrote:
> Thanks Nils.
> It turns out the problem concerns any text output from R, not only
> error messages.
> In each case R code is being evaluated (ex. values of variables
> change),
> however no sign of feedback from R if the input is too long.
A related
Thanks Nils.
It turns out the problem concerns any text output from R, not only
error messages.
In each case R code is being evaluated (ex. values of variables
change),
however no sign of feedback from R if the input is too long.
sage: Ri.eval(('#1')**100+"\n print(1)")
'\n[1] 1'
sage: Ri.eval(('#
As it turns out, experimentation is very easy:
sage: Ri=R()
sage: Ri.eval(("#1"**100+"\n")**10+"]")
''
sage: Ri.eval(("#1"**100+"\n")**10+"]",allow_use_file=False)
'\n\n\n\n\n\n\n\n\n\nError: unexpected \']\' in "]"'
sage: Ri.eval(("#1"**100+"\n")**10+"]",split_lines=True)
'\n\n\n\n\n\n\n\n\n\nErr
On May 20, 7:12 am, Maciek Sykulski wrote:
> Hi All,
>
> I've compiled from source sage-5.0 on Gentoo on the following machine:
> Linux 3.2.6 #3 SMP Thu Feb 16 17:40:05 CET 2012 x86_64 Intel(R)
> Xeon(R) CPU X5690 @ 3.47GHz GenuineIntel GNU/Linux
>
> Everything seems to work fine except for this:
