PPS: It looks like the system is totally corrupted now after trying running
top level sage without running configure.
'make all' now finished in 10 minutes with log files in logs/pkgs of 0
bytes.
Please advise how to clean up the sage system, should ~/.sage be removed?
Thank you for your help.
On
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,
/