#20388: Fix the Magma interface to work with remote installations
-------------------------------------+-------------------------------------
Reporter: mmasdeu | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-7.2
Component: interfaces: | Resolution:
optional | Merged in:
Keywords: magma, remote | Reviewers:
Authors: Marc Masdeu | Work issues:
Report Upstream: N/A | Commit:
Branch: u/mmasdeu/20388 | da0c8a128c83b89f9cc6f42b3dfcdcac3f8fce24
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:14 nbruin]:
> I think the `set_magma_session` is a rather heavy interface. It seems to
me the appropriate place would be a method on
`sage.interfaces.expect.Expect` along the lines of
> {{{
> def set_server_and_command(self,server,command):
> if self._expect:
> raise RuntimeError("interface has already started")
> self._server = server
> self.__command = command
> }}}
I like better this approach. That way the server can even be configured in
`init.sage`!
> The cleaner solution would be to make new `Magma` instances for
different server/command settings, but as we've seen a lot of code assumes
that there is a single, global, magma instance for default use throughout
the lifetime of a sage session.
I would actually remove the `Magma` from the global namespace. That would
not prevent anyone from testing different versions.
--
Ticket URL: <http://trac.sagemath.org/ticket/20388#comment:15>
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.
