Skip to content

make it so the magma .sig files in extcode don't get written there by magma #5041

@williamstein

Description

@williamstein

If one installs sage sytem wide, and a user tries to run any magma commands, and the .sig files aren't written in data/extcode/magma, then BOOM! This is a total show stopper for any "normal users" to use the sage magma interface for anything serious. This must be FIXED!

To fix this, when the magma interface is first run, make sure to copy the .m files over to $DOT_SAGE/magma first and load from there. One will have to do the copy the first time the magma interface is started in any magma session. alternatively, one could try: except: the magma.load command, and if it fails, then try to copy and load from /tmp/, say or DOT_SAGE/temp/. Maybe the second idea is cleaner.

Component: interfaces

Issue created by migration from https://trac.sagemath.org/ticket/5041

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions