On Monday, May 16, 2022 at 9:12:53 PM UTC-7 hohoa...@gmail.com wrote:
> Is it this snippet, would you please elaborate?
>
>
> # Make sure that SAGE_ROOT is either an absolute physical directory name
> # or empty.
> if [ -n "$SAGE_ROOT" ]; then
> export SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null
Hi,
Is it this snippet, would you please elaborate?
# Make sure that SAGE_ROOT is either an absolute physical directory name
# or empty.
if [ -n "$SAGE_ROOT" ]; then
export SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)
fi
BTW, it is rather confusing to see in '$SAGE_LOCAL/bin/sage':
On Monday, May 16, 2022 at 8:07:48 PM UTC-7 hohoa...@gmail.com wrote:
> Please advise the use of SAGE_ROOT when it is exported
> from '$SAGE_LOCAL/bin/sage':
>
> # Determine SAGE_ROOT, SAGE_LOCAL, and SAGE_VENV.
> unset SAGE_VENV
> if [ -x "${SELF}-config" ]; then
> # optional sage-config co
Dear All,
Please advise the use of SAGE_ROOT when it is exported
from '$SAGE_LOCAL/bin/sage':
# Determine SAGE_ROOT, SAGE_LOCAL, and SAGE_VENV.
unset SAGE_VENV
if [ -x "${SELF}-config" ]; then
# optional sage-config console script, installed by sage_conf
export SAGE_ROOT=$("${SELF}-conf
And trivial https://trac.sagemath.org/ticket/33859 is ready for review.
> On 17/05/2022, at 12:24, François Bissey wrote:
>
> Right, I’ll open a ticket for that.
>
>> On 17/05/2022, at 12:11, Matthias Koeppe wrote:
>>
>> It looks like this directory was removed in #27155, so this line can be
Right, I’ll open a ticket for that.
> On 17/05/2022, at 12:11, Matthias Koeppe wrote:
>
> It looks like this directory was removed in #27155, so this line can be
> removed from MANIFEST.in
>
>
> On Monday, May 16, 2022 at 4:31:50 PM UTC-7 François Bissey wrote:
> Hi,
>
> I have noticed it b
It looks like this directory was removed in #27155, so this line can be
removed from MANIFEST.in
On Monday, May 16, 2022 at 4:31:50 PM UTC-7 François Bissey wrote:
> Hi,
>
> I have noticed it before but I have only started to wonder about it while
> preparing the 9.6 release for Gentoo.
> Duri
Hi,
I have noticed it before but I have only started to wonder about it while
preparing the 9.6 release for Gentoo.
During the install phase while the wheel is being prepared I have the following
messages
listing git files failed - pretending there aren't any
warning: no files found matching '*
Please take a look at the notes for the Apple Silicon platform
at https://trac.sagemath.org/wiki/ReleaseTours/sage-9.6#Sources
If the problem persists, please send the top-level config.log file
On Saturday, May 14, 2022 at 1:14:12 PM UTC-7 ijoll...@gmail.com wrote:
> Hi,
>
> I am very new to Sa
Hi,
"""
We change the bootstrap scripts so that they invoke
build/bin/sage-package directly
instead of going through the SAGE_ROOT/sage script.
"""
This is great news, a big time saver. Thank you so much.
Until then, this hitchhiker needs to restore the original
'$SAGE_ROOT/sage' before she can
On Monday, May 16, 2022 at 1:35:37 AM UTC-7 hohoa...@gmail.com wrote:
> [...] $SAGE_ROOT/sage [...]
>
The positively reviewed tickets https://trac.sagemath.org/ticket/33786
and https://trac.sagemath.org/ticket/33787 make changes to this script. You
may find these changes and the discussion on
El lunes, 16 de mayo de 2022 a las 17:34:14 UTC+2, Ricardo Buring escribió:
> Specifically bliss::AbstractGraph::canonical_form calls
> bliss::AbstractGraph::search, which sometimes calls
> bliss::Partition::cr_init without calling bliss::Partition::cr_free, due
> to a (conditional) early retur
On Mon, May 16, 2022 at 8:03 AM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> I would say that code with parallel computations + cypari2 should not
> be merged (as cypari2 does not support it).
is it parallel multiprocessing, or parallel multithreading?
>
> If you need parallel + PARI
P.S: Sorry, there was a typo, "$SAGE_LOCAL/sage" should read
"$SAGE_LOCAL/bin/sage"
On Mon, May 16, 2022 at 4:35 AM ph h wrote:
> Dear All,
>
> Please find appended below a snippet from $SAGE_ROOT/sage.
>
> Would it be nice if "$SAGE_LOCAL/sage" could be used without assumptions
> instead of "
Dear All,
Please find appended below a snippet from $SAGE_ROOT/sage.
Would it be nice if "$SAGE_LOCAL/sage" could be used without assumptions
instead of "$SAGE_ROOT/local/bin/sage" with the assumption that 'SAGE_LOCAL
is the "local" subdirectory'
BTW, should "$SAGE_LOCAL/sage" be the first c
I would say that code with parallel computations + cypari2 should not
be merged (as cypari2 does not support it).
If you need parallel + PARI then use the C library directly with the
appropriate threads locks.
If the problem comes from somewhere else, then it would better be sorted
out.
Best
Vi
16 matches
Mail list logo
