#20388: Fix the Magma interface to work with remote installations
------------------------------------+---------------------------------
Reporter: mmasdeu | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-7.2
Component: interfaces: optional | Keywords: magma, remote
Merged in: | Authors: Marc Masdeu
Reviewers: | Report Upstream: N/A
Work issues: | Branch:
Commit: | Dependencies:
Stopgaps: |
------------------------------------+---------------------------------
I have frequently encountered computer setups where one has access to a
Sage installation locally, but Magma is only installed in a remote machine
(say with address 'remote'). Typically one either:
1) Logs into 'remote' via ssh and does some computation in Magma.
2) uses the ssh command
{{{
$> ssh -t remote 'magma'
}}}
to pretend having magma installed locally.
Actually Sage has functionality to use (2) in its interface with Magma,
but it is currently broken and not advertised. It presumes that 'remote'
also has sage installed (in fact it presumes that sage-native-execute is
in the default PATH), for example.
This ticket fixes this, and makes a command like
{{{
sage: magma = Magma(server = 'remote', command = 'magma-myversion')
}}}
work, and provide the user with an interface to a particular version of
Magma installed in 'remote'.
--
Ticket URL: <http://trac.sagemath.org/ticket/20388>
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.
