#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:12 mmasdeu]:
> Here is what I propose: add the environment variables (which make sense
the moment there is a magma = Magma() line in there...), but also change
the functions using magma to use the get_magma_session() function. How
reasonable is this?
You are right that it is desirable to have a way to modify it from Sage
itself. However, I would not populate the global namespace with
`get_magma_session` unless the global `magma` is deprecated (which can be
done using lazy imports).
Moreover, it is very confusing to have all of: `magma`, `Magma`,
`magma_free`, `magma_console`, `magma_version` in the global namespace...
(not talking about `Magmas`). A cleanup is desirable.
--
Ticket URL: <http://trac.sagemath.org/ticket/20388#comment:13>
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.
