"configure" was deliberately made a separate, manual step because users
need to read (and act upon) its output.
On Sunday, April 24, 2022 at 10:21:45 PM UTC-7 hohoa...@gmail.com wrote:
> P.S:
> """
> Everyone wants the top-level "sage" script to work out of the box
> without being configured, b
P.S:
"""
Everyone wants the top-level "sage" script to work out of the box
without being configured, built, or installed
"""
> Maybe experienced users in this camp can share some undocumented use case
scenarios?
While waiting for someone to share their secrets, It was found that the
"advanced i
If they indeed haven't run `./configure`, then they should. I think it's
not too much to ask someone to read the README file before trying to build
Sage. If they have already run `./configure`, then the error message needs
to be fixed.
On Sunday, April 24, 2022 at 7:19:45 PM UTC-7 Matthias Koep
The error message could be improved. I've
opened https://trac.sagemath.org/ticket/33753 for this.
On Sunday, April 24, 2022 at 5:36:04 PM UTC-7 hohoa...@gmail.com wrote:
> Dear All,
>
> Someone is trying to build and run 'sage' with this advanced incantation
> 'sage -br'
>
> ~/sage-9.6/rc0.mod
Hi Thomas,
Could the memleak be coming from within bliss?
Best,
Travis
On Sunday, April 24, 2022 at 1:50:26 AM UTC+9 t.will...@gmail.com wrote:
> Dear all,
>
> there seems to be a memory leak in canonical_label(...), using bliss.
> Here is a test script to demonstrate the problem:
>
> --
Dear All,
Someone is trying to build and run 'sage' with this advanced incantation
'sage -br'
~/sage-9.6/rc0.mod2$ sage.GOOD/sage -br
and she was asked " Did you run configure?"
Unfortunately, "sage --advanced" does not give any incantation for this
('sage -c' is NOT for 'configure')
She is
the following works with Sage 9.6.rc1
sage: t=libgap.function_factory('''function()
: local Q, KQ, rel, A;
: LoadPackage("qpa");
: Q:=Quiver(3,[[1,2,"a"],[2,3,"b"]]);
: KQ:=PathAlgebra(GF(3),Q);
: AssignGeneratorVariables(KQ);
: rel:=[a*b];
: A:=KQ/rel;
: return A;
P.S: It happened because sage was run before 'make configure' was done
~/sage-9.6$ git/sage.mod/sage
On Sun, Apr 24, 2022 at 5:43 PM ph h wrote:
> Dear All,
>
> When is it safe to clean up '~./.sage' ?
> How can 'sage-cleaner' be invoked manually?
> Why is it invoked because of 'ModuleNotFoun
Dear All,
When is it safe to clean up '~./.sage' ?
How can 'sage-cleaner' be invoked manually?
Why is it invoked because of 'ModuleNotFoundError: No module named 'sage'?
Please find appended below the console output
Regards,
phiho
Sourcing /home/hph/sage-9.6/git/sage.mod/resolvelinks.dot,
/
This has been reported at https://github.com/sagemath/sagecell/issues/560
but as far as I can see is the problem of GAP interface in Sage itself.
Perhaps somebody familiar with it may want to take a look ;-)
--
You received this message because you are subscribed to the Google Groups
"sage-dev
10 matches
Mail list logo
