#17230: create a pexpect interface to julia
-------------------------------------+-------------------------------------
Reporter: was | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: sage-6.4
Component: interfaces: | Resolution:
optional | Merged in:
Keywords: | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: public/17230 | 26e806028f37c45590040990174265354efe00a5
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Description changed by was:
Old description:
> I spent a few hours writing a pexpect interface to Julia. There's no
> doctests, and I had to do some odd things to make it work well (e.g.,
> using vt100 mode for the TERM so that errors get reported! actually
> making use of the control codes for much, much better synchronization;
> putting in a bunch of \n's to ensure that opening strings don't hang the
> interface). I'm too busy to doctest this and "do everything right" for
> Sage, but maybe somebody else wants to. I think there is potential value
> for some users in having a pexpect Julia interface in Sage, since it
> makes it possible to easily move (small) data back and forth between
> systems, compare algorithms implemented in both, etc. As with all the
> other interfaces, something at the C library level can be much faster and
> more scalable... but *both* approaches have unique value (in my opinion).
>
> I'm attaching some code to this ticket, which I've GPL'd. I do not
> intend to spend more time on this ticket.
New description:
I spent a few hours writing a pexpect interface to Julia. There's no
doctests, and I had to do some odd things to make it work well (e.g.,
using vt100 mode for the TERM so that errors get reported! actually making
use of the control codes for much, much better synchronization; putting in
a bunch of \n's to ensure that opening strings don't hang the interface).
I'm too busy to doctest this and "do everything right" for Sage, but maybe
somebody else wants to. I think there is potential value for some users
in having a pexpect Julia interface in Sage, since it makes it possible to
easily move (small) data back and forth between systems, compare
algorithms implemented in both, etc. As with all the other interfaces,
something at the C library level can be much faster and more scalable...
but *both* approaches have unique value (in my opinion).
Link to code for this in SMC:
https://github.com/sagemathinc/smc/blob/master/src/smc_sagews/smc_sagews/julia.py
--
--
Ticket URL: <http://trac.sagemath.org/ticket/17230#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
