-
-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve and document GAP and libgap memory customisation #34041
Comments
Author: Dima Pasechnik |
New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:4
-1 on using |
comment:5
Also, the naming scheme used by sage.interfaces gives |
comment:7
Replying to @mkoeppe:
downstreams don't like sage.env, do they? |
comment:8
The module |
comment:9
I love Now, I am not really against using |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
Thanks for making this change, LGTM |
comment:13
(but I haven't tested it, so let's wait for the patchbot or the Build&test workflow) |
This comment has been minimized.
This comment has been minimized.
comment:15
Tested locally, seems to work fine. I was able to provoke errors in the testsuite by setting a low memory limit |
Reviewer: Matthias Koeppe |
Changed branch from u/dimpase/interfaces/gap_allow_memory_settings to |
it's a FAQ, how to do this. Should be fixed, and a working solution provided.
one can test this by exporting env.vars
SAGE_GAP_MEMORY
and/orSAGE_GAP_COMMAND
(details in the branch`), before testing, e.g.CC: @kiwifb
Component: interfaces
Author: Dima Pasechnik
Branch/Commit:
e6ef4fe
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/34041
The text was updated successfully, but these errors were encountered: