date:20220525

[sage-devel] Virtual Sage Days June 1–3: Preliminary program, Registration

2022-05-25 Thread Matthias Koeppe

Preliminary program:
https://researchseminars.org/seminar/SageDays112358

Please register:
https://sagemath.zulipchat.com/#narrow/stream/321245-sd112.2E358/topic/Registration

It is still possible to contribute talks, tutorials, coding sprints, and 
other activities

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b94af80d-9ece-42f7-9f26-9b847f9af9a7n%40googlegroups.com.

Re: [sage-devel] Re: Run the actual Sage script

2022-05-25 Thread Matthias Koeppe

https://trac.sagemath.org/ticket/33852

On Wednesday, May 25, 2022 at 10:13:38 PM UTC-7 hohoa...@gmail.com wrote:

> Hi,
>
> """
> We change the bootstrap scripts so that they invoke build/bin/sage-package 
> directly 
> instead of going through the SAGE_ROOT/sage script.
> """
>
> It would be nice if usage_advanced() and sage_version() could be factored 
> out of src/bin/sage so that the src/doc/bootstrap can be completely 
> independent of SAGE_ROOT/sage:
>
> # ./sage -advanced> "$OUTPUT"
>
> SAGE_ROOT="$(pwd)"
> . "src/bin/sage-version" 
> . "src/bin/sage-usage_advanced"  > "$OUTPUT"
>
> Is there a better way to achieve this?
>
> Thank you for your help.
>
> Regards,
>
> phiho
>
>
> On Mon, May 16, 2022 at 1:31 PM ph h  wrote:
>
>> 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 'make configure' ('bootstrap' requires 
>> that original 'sage') while testing 'configure.ac'
>>
>> Best regards,
>>
>> phiho
>>
>>
>> On Mon, May 16, 2022 at 12:24 PM Matthias Koeppe  
>> wrote:
>>
>>> 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 the ticket interesting.
>>>
>>> https://trac.sagemath.org/ticket/33852 makes other changes related to 
>>> the script. It needs review.
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sage-devel+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/ec09cac9-4037-477b-968c-25f2ded19d54n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/165486a6-7add-4795-bf7f-2d5dc2bcf47an%40googlegroups.com.

Re: [sage-devel] Re: Run the actual Sage script

2022-05-25 Thread ph h

Hi,

"""
We change the bootstrap scripts so that they invoke
build/bin/sage-package directly
instead of going through the SAGE_ROOT/sage script.
"""

It would be nice if usage_advanced() and sage_version() could be factored
out of src/bin/sage so that the src/doc/bootstrap can be completely
independent of SAGE_ROOT/sage:

# ./sage -advanced> "$OUTPUT"

SAGE_ROOT="$(pwd)"
. "src/bin/sage-version"
. "src/bin/sage-usage_advanced"  > "$OUTPUT"

Is there a better way to achieve this?

Thank you for your help.

Regards,

phiho


On Mon, May 16, 2022 at 1:31 PM ph h  wrote:

> 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 'make configure' ('bootstrap' requires
> that original 'sage') while testing 'configure.ac'
>
> Best regards,
>
> phiho
>
>
> On Mon, May 16, 2022 at 12:24 PM Matthias Koeppe 
> wrote:
>
>> 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 the ticket interesting.
>>
>> https://trac.sagemath.org/ticket/33852 makes other changes related to
>> the script. It needs review.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/ec09cac9-4037-477b-968c-25f2ded19d54n%40googlegroups.com
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CALZQg1YALv8fEYUO1YNi%3DbmH5m_G4oMXioRZnxrj70ywUOZeow%40mail.gmail.com.

Re: [sage-devel] [ 1 = 1+0i ] <=> [ 1 = 1 ]

2022-05-25 Thread John H Palmieri

Are you asking whether a shell script can handle complex arithmetic? What 
does that have to do with Sage?

If that's not what you're asking, please clarify.

On Wednesday, May 25, 2022 at 5:38:43 AM UTC-7 hohoa...@gmail.com wrote:

> P.S: Sorry, there was a typo here:
> *# at configuration time.*
>
> should read
>
> *# at validating time.*
>
>
> On Tue, May 24, 2022 at 10:14 PM ph h  wrote:
>
>> Dear All,
>>
>> Is this feasible [ 1 = 1+0i  ] <=> [ 1 = 1 ] ?
>>
>> Regards,
>>
>> phiho
>>
>> **
>> if [ 1 = 1+0i ]; then  
>> # Make sure that SAGE_ROOT is either an absolute physical directory name
>> # or empty.
>> *# An absolute physical directory name has already been embedded and 
>> exported*
>>
>>
>>
>>
>>
>> *# at configuration time.#if [ -n "$SAGE_ROOT" ]; then#export 
>> SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)#fi#if [ -d "$SAGE_ROOT" 
>> ]; then*
>> export SAGE_LOGS="$SAGE_ROOT/logs/pkgs"
>> export SAGE_SRC="$SAGE_ROOT/src"
>> export SAGE_DOC_SRC="$SAGE_SRC/doc"
>> export PATH="$SAGE_ROOT/build/bin:$PATH"
>> if [ -z "$SAGE_DISTFILES" ]; then
>> SAGE_DISTFILES="$SAGE_ROOT/upstream"
>> export SAGE_DISTFILES
>> fi
>> if [ -z "$CCACHE_BASEDIR" ]; then
>> export CCACHE_BASEDIR="$SAGE_ROOT"
>> fi
>> *#fi*
>> fi# [ 1 = 1+0i ]
>>
>> **
>>
>> **
>> if [ 1 = 1 ]; then
>> # 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
>> [...]
>> if [ -d "$SAGE_ROOT" ]; then
>> export SAGE_LOGS="$SAGE_ROOT/logs/pkgs"
>> export SAGE_SRC="$SAGE_ROOT/src"
>> fi
>> [...]
>> if [ -n "$SAGE_SRC" ]; then
>> export SAGE_DOC_SRC="$SAGE_SRC/doc"
>> fi
>> [...]
>> if [ -d "$SAGE_ROOT" ]; then
>> export PATH="$SAGE_ROOT/build/bin:$PATH"
>> fi
>> [...]
>> if [ -d "$SAGE_ROOT" ]; then
>> if [ -z "$SAGE_DISTFILES" ]; then
>> SAGE_DISTFILES="$SAGE_ROOT/upstream"
>> export SAGE_DISTFILES
>> fi
>> fi
>> [...]
>> if [ -d "$SAGE_ROOT" -a -z "$CCACHE_BASEDIR" ]; then
>> export CCACHE_BASEDIR="$SAGE_ROOT"
>> fi
>> fi  # [ 1 = 1 ]
>>
>> if [ 1 = 2 ]; then
>> echo "The following enviroment variables can be set by the user"
>> echo "AR  The archiver (e.g. ar, /usr/ccs/bin/ar or 
>> /usr/bin/ar)"
>> echo "AS  The assembler (e.g. as, /usr/ccs/bin/as or 
>> /usr/bin/as)"
>> echo "CC  The C compiler (e.g cc, /opt/SUNWspro/bin/cc or 
>> /usr/bin/gcc)"
>> echo "CFLAGS  Flag(s) for the C compiler (e.g.  -g -Wall -O2)"
>> echo "(You are advised to a some optimisation flag(s), 
>> such as -O2 or -xO2 to CFLAGS)"
>> echo "CXX The C++ compiler (e.g g++, /opt/SUNWspro/bin/CC or 
>> /usr/local/bin/g++)"
>> echo "CXXFLAGSFlag(s) for the C++ compiler (e.g. -fast -fsimple=1 
>> -x04)"
>> echo "LD  The linker (e.g. ld, /usr/ccs/bin/ld or 
>> /usr/bin/ld)"
>> echo "LDFLAGS Linker flag(s) (e.g. -D token)"
>> echo "LN  Used to make links (e.g. ln, /usr/xpg4/bin/ln or 
>> /usr/bin/ln)"
>> echo "MAKEThe make program (e.g. make, /usr/bin/make or 
>> /usr/local/bin/gmake)"
>> echo "MAKEFLAGS   Flag(s) to make (e.g. -j4)."
>> echo "RANLIB  Archiver ranlib (e.g. ranlib, /usr/ccs/bin/ranlib 
>> etc)"
>> echo "SHAREDFLAGS Flag(s) necessary for building a shared library 
>> (e.g. -fPIC or -xcode=pic32)"
>> echo "We attempt to set this to sensible values, but check below to"
>> echo "ensure they are OK. If you wish to override any then please 
>> use:"
>> echo "setenv NAME_OF_ENVIROMENT_VARIABLE value_of_enviroment_variable"
>> echo "(if you use tcsh, csh or a similar shell) or"
>> echo "NAME_OF_ENVIROMENT_VARIABLE value_of_enviroment_variable"
>> echo "export NAME_OF_ENVIROMENT_VARIABLE"
>> echo "if you use sh, bash or a similar shell"
>> fi
>> **
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/0e5b5d21-9dda-492a-b427-ea0d7104505an%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/92ccd062-1c2e-4b7c-b85e-eaca33a3a7fbn%40googlegroups.com.

Re: [sage-devel] error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

2022-05-25 Thread Dima Pasechnik

PS. Somehow we know for years that 'tedder' is buggy, see
https://trac.sagemath.org/ticket/25872
but did not take an action. Sorry :-(

On Wed, May 25, 2022 at 5:19 PM Dima Pasechnik  wrote:
>
> On Wed, May 25, 2022 at 2:17 PM Anne-Aymone BOURGUIN
>  wrote:
> >
> > Hello,
> > I am using the sage.graphs.graph_decompositions.modular_decomposition with 
> > two configurations :
> > * a Windows (64-bit) system, with sage 9.3 installed (Python 3.7.10)
> > * an Ubuntu (64-bit) system, with sage 9.5 installed (Python 3.8.10)
> > I was working with sage 9.0 on Ubuntu until I noticed differences between 
> > the modular decompositions that I got from my different computers.
> > At that time, I noticed that it was the 9.0 version which gave me wrong 
> > decompositions, so I installed the 9.5 version.
> >
> > Now, I still have some errors :
> > I use the modular_decomposition function without optional parameters, so 
> > it's the "habib" algorithm that is used...
> >
> > I'm joining my code to this message.
> > The example that I'm sending today is pretty easy to check by hand, and we 
> > can see that the modular decomposition is not what it should be.
> >
> > In case the file is not opening, the example is just :
> > d = {
> > 1  :  [2, 3, 4],
> > 2  :  [1, 3, 4],
> > 3  :  [1, 2, 4],
> > 4  :  [1, 2, 3, 5],
> > 5  :  [10, 4, 6, 7, 8, 9],
> > 6  :  [5, 7],
> > 7  :  [5, 6, 8, 9],
> > 8  :  [5, 7, 9],
> > 9  :  [10, 5, 7, 8],
> > 10  :  [5, 9]
> > }
> >g = Graph(d)
> >
> > And modular_decomposition(g) gives me :
> > PRIME
> >  5
> >  SERIES
> >   9
> >   PARALLEL
> >10
> >7
> >8
> >6
> >  4
> >  SERIES
> >   3
> >   2
> >   1
> > (6 and 9 should not be neighbors, but they are in this modular 
> > decomposition)
>
> On Sage 9.6, I get
>
> sage: g.modular_decomposition()
> (PRIME, [5, 4, (SERIES, [1, 2, 3]), (PRIME, [9, 7, 6, 8, 10])])
>
> sage: g.modular_decomposition(algorithm='tedder')
> (PRIME, [5, (SERIES, [9, (PARALLEL, [10, 7, 8, 6])]), 4, (SERIES, [3, 2, 1])])
>
> It appears that the 1st output is correct (that's the default,
> 'habib', algorithm), and
> the 2nd (with 'tedder')  is not.
>
> 'habib' was added in https://trac.sagemath.org/ticket/26496
> - and this seems to be the 1st example we know where our 'tedder' is wrong.
>
> I've opened https://trac.sagemath.org/ticket/33902 to deal with this.
>
> Dima
>
>
>
>
> >
> > Best regards,
> > Anne-Aymone Bourguin
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to sage-devel+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-devel/4df9a528-ca41-4f71-9c7e-3543047b9c05n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1gryfK3LWnE14p%3D7NPVQirCRvjQed_DfNSu2ebS2f8qQ%40mail.gmail.com.

Re: [sage-devel] error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

2022-05-25 Thread Dima Pasechnik

On Wed, May 25, 2022 at 2:17 PM Anne-Aymone BOURGUIN
 wrote:
>
> Hello,
> I am using the sage.graphs.graph_decompositions.modular_decomposition with 
> two configurations :
> * a Windows (64-bit) system, with sage 9.3 installed (Python 3.7.10)
> * an Ubuntu (64-bit) system, with sage 9.5 installed (Python 3.8.10)
> I was working with sage 9.0 on Ubuntu until I noticed differences between the 
> modular decompositions that I got from my different computers.
> At that time, I noticed that it was the 9.0 version which gave me wrong 
> decompositions, so I installed the 9.5 version.
>
> Now, I still have some errors :
> I use the modular_decomposition function without optional parameters, so it's 
> the "habib" algorithm that is used...
>
> I'm joining my code to this message.
> The example that I'm sending today is pretty easy to check by hand, and we 
> can see that the modular decomposition is not what it should be.
>
> In case the file is not opening, the example is just :
> d = {
> 1  :  [2, 3, 4],
> 2  :  [1, 3, 4],
> 3  :  [1, 2, 4],
> 4  :  [1, 2, 3, 5],
> 5  :  [10, 4, 6, 7, 8, 9],
> 6  :  [5, 7],
> 7  :  [5, 6, 8, 9],
> 8  :  [5, 7, 9],
> 9  :  [10, 5, 7, 8],
> 10  :  [5, 9]
> }
>g = Graph(d)
>
> And modular_decomposition(g) gives me :
> PRIME
>  5
>  SERIES
>   9
>   PARALLEL
>10
>7
>8
>6
>  4
>  SERIES
>   3
>   2
>   1
> (6 and 9 should not be neighbors, but they are in this modular decomposition)

On Sage 9.6, I get

sage: g.modular_decomposition()
(PRIME, [5, 4, (SERIES, [1, 2, 3]), (PRIME, [9, 7, 6, 8, 10])])

sage: g.modular_decomposition(algorithm='tedder')
(PRIME, [5, (SERIES, [9, (PARALLEL, [10, 7, 8, 6])]), 4, (SERIES, [3, 2, 1])])

It appears that the 1st output is correct (that's the default,
'habib', algorithm), and
the 2nd (with 'tedder')  is not.

'habib' was added in https://trac.sagemath.org/ticket/26496
- and this seems to be the 1st example we know where our 'tedder' is wrong.

I've opened https://trac.sagemath.org/ticket/33902 to deal with this.

Dima




>
> Best regards,
> Anne-Aymone Bourguin
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/4df9a528-ca41-4f71-9c7e-3543047b9c05n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq1x1VringXcCAWg%2BFLeAAVc0UeGHZZa3YEf82BM%2B3pnEw%40mail.gmail.com.

[sage-devel] Re: error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

2022-05-25 Thread Anne-Aymone BOURGUIN

I'm sorry, a little confusion on my part : I don't know which algorithm is 
used in this function (habib or tedder or ?...).

Le mercredi 25 mai 2022 à 15:17:41 UTC+2, Anne-Aymone BOURGUIN a écrit :

> Hello,
> I am using the sage.graphs.graph_decompositions.modular_decomposition with 
> two configurations :
> * a Windows (64-bit) system, with sage 9.3 installed (Python 3.7.10)
> * an Ubuntu (64-bit) system, with sage 9.5 installed (Python 3.8.10)
> I was working with sage 9.0 on Ubuntu until I noticed differences between 
> the modular decompositions that I got from my different computers.
> At that time, I noticed that it was the 9.0 version which gave me wrong 
> decompositions, so I installed the 9.5 version.
>
> Now, I still have some errors :
> I use the modular_decomposition function without optional parameters, so 
> it's the "habib" algorithm that is used...
>
> I'm joining my code to this message.
> The example that I'm sending today is pretty easy to check by hand, and we 
> can see that the modular decomposition is not what it should be.
>
> In case the file is not opening, the example is just :
> d = {
> 1  :  [2, 3, 4],
> 2  :  [1, 3, 4],
> 3  :  [1, 2, 4],
> 4  :  [1, 2, 3, 5],
> 5  :  [10, 4, 6, 7, 8, 9],
> 6  :  [5, 7],
> 7  :  [5, 6, 8, 9],
> 8  :  [5, 7, 9],
> 9  :  [10, 5, 7, 8],
> 10  :  [5, 9]
> }
>g = Graph(d)
>
> And modular_decomposition(g) gives me :
> PRIME
>  5
>  SERIES
>   9
>   PARALLEL
>10
>7
>8
>6
>  4
>  SERIES
>   3
>   2
>   1
> (6 and 9 should not be neighbors, but they are in this modular 
> decomposition)
>
> Best regards,
> Anne-Aymone Bourguin
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/b860c8ad-19f5-487c-9392-b071b1d4b8e3n%40googlegroups.com.

[sage-devel] error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

2022-05-25 Thread Anne-Aymone BOURGUIN

Hello,
I am using the sage.graphs.graph_decompositions.modular_decomposition with 
two configurations :
* a Windows (64-bit) system, with sage 9.3 installed (Python 3.7.10)
* an Ubuntu (64-bit) system, with sage 9.5 installed (Python 3.8.10)
I was working with sage 9.0 on Ubuntu until I noticed differences between 
the modular decompositions that I got from my different computers.
At that time, I noticed that it was the 9.0 version which gave me wrong 
decompositions, so I installed the 9.5 version.

Now, I still have some errors :
I use the modular_decomposition function without optional parameters, so 
it's the "habib" algorithm that is used...

I'm joining my code to this message.
The example that I'm sending today is pretty easy to check by hand, and we 
can see that the modular decomposition is not what it should be.

In case the file is not opening, the example is just :
d = {
1  :  [2, 3, 4],
2  :  [1, 3, 4],
3  :  [1, 2, 4],
4  :  [1, 2, 3, 5],
5  :  [10, 4, 6, 7, 8, 9],
6  :  [5, 7],
7  :  [5, 6, 8, 9],
8  :  [5, 7, 9],
9  :  [10, 5, 7, 8],
10  :  [5, 9]
}
   g = Graph(d)

And modular_decomposition(g) gives me :
PRIME
 5
 SERIES
  9
  PARALLEL
   10
   7
   8
   6
 4
 SERIES
  3
  2
  1
(6 and 9 should not be neighbors, but they are in this modular 
decomposition)

Best regards,
Anne-Aymone Bourguin

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/4df9a528-ca41-4f71-9c7e-3543047b9c05n%40googlegroups.com.


modular_decomposition_problem.sage
Description: Binary data

Re: [sage-devel] [ 1 = 1+0i ] <=> [ 1 = 1 ]

2022-05-25 Thread ph h

P.S: Sorry, there was a typo here:
*# at configuration time.*

should read

*# at validating time.*


On Tue, May 24, 2022 at 10:14 PM ph h  wrote:

> Dear All,
>
> Is this feasible [ 1 = 1+0i  ] <=> [ 1 = 1 ] ?
>
> Regards,
>
> phiho
>
> **
> if [ 1 = 1+0i ]; then
> # Make sure that SAGE_ROOT is either an absolute physical directory name
> # or empty.
> *# An absolute physical directory name has already been embedded and
> exported*
>
>
>
>
>
> *# at configuration time.#if [ -n "$SAGE_ROOT" ]; then#export
> SAGE_ROOT=$(cd "$SAGE_ROOT" 2>/dev/null && pwd -P)#fi#if [ -d "$SAGE_ROOT"
> ]; then*
> export SAGE_LOGS="$SAGE_ROOT/logs/pkgs"
> export SAGE_SRC="$SAGE_ROOT/src"
> export SAGE_DOC_SRC="$SAGE_SRC/doc"
> export PATH="$SAGE_ROOT/build/bin:$PATH"
> if [ -z "$SAGE_DISTFILES" ]; then
> SAGE_DISTFILES="$SAGE_ROOT/upstream"
> export SAGE_DISTFILES
> fi
> if [ -z "$CCACHE_BASEDIR" ]; then
> export CCACHE_BASEDIR="$SAGE_ROOT"
> fi
> *#fi*
> fi# [ 1 = 1+0i ]
>
> **
>
> **
> if [ 1 = 1 ]; then
> # 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
> [...]
> if [ -d "$SAGE_ROOT" ]; then
> export SAGE_LOGS="$SAGE_ROOT/logs/pkgs"
> export SAGE_SRC="$SAGE_ROOT/src"
> fi
> [...]
> if [ -n "$SAGE_SRC" ]; then
> export SAGE_DOC_SRC="$SAGE_SRC/doc"
> fi
> [...]
> if [ -d "$SAGE_ROOT" ]; then
> export PATH="$SAGE_ROOT/build/bin:$PATH"
> fi
> [...]
> if [ -d "$SAGE_ROOT" ]; then
> if [ -z "$SAGE_DISTFILES" ]; then
> SAGE_DISTFILES="$SAGE_ROOT/upstream"
> export SAGE_DISTFILES
> fi
> fi
> [...]
> if [ -d "$SAGE_ROOT" -a -z "$CCACHE_BASEDIR" ]; then
> export CCACHE_BASEDIR="$SAGE_ROOT"
> fi
> fi  # [ 1 = 1 ]
>
> if [ 1 = 2 ]; then
> echo "The following enviroment variables can be set by the user"
> echo "AR  The archiver (e.g. ar, /usr/ccs/bin/ar or
> /usr/bin/ar)"
> echo "AS  The assembler (e.g. as, /usr/ccs/bin/as or
> /usr/bin/as)"
> echo "CC  The C compiler (e.g cc, /opt/SUNWspro/bin/cc or
> /usr/bin/gcc)"
> echo "CFLAGS  Flag(s) for the C compiler (e.g.  -g -Wall -O2)"
> echo "(You are advised to a some optimisation flag(s),
> such as -O2 or -xO2 to CFLAGS)"
> echo "CXX The C++ compiler (e.g g++, /opt/SUNWspro/bin/CC or
> /usr/local/bin/g++)"
> echo "CXXFLAGSFlag(s) for the C++ compiler (e.g. -fast -fsimple=1
> -x04)"
> echo "LD  The linker (e.g. ld, /usr/ccs/bin/ld or /usr/bin/ld)"
> echo "LDFLAGS Linker flag(s) (e.g. -D token)"
> echo "LN  Used to make links (e.g. ln, /usr/xpg4/bin/ln or
> /usr/bin/ln)"
> echo "MAKEThe make program (e.g. make, /usr/bin/make or
> /usr/local/bin/gmake)"
> echo "MAKEFLAGS   Flag(s) to make (e.g. -j4)."
> echo "RANLIB  Archiver ranlib (e.g. ranlib, /usr/ccs/bin/ranlib
> etc)"
> echo "SHAREDFLAGS Flag(s) necessary for building a shared library
> (e.g. -fPIC or -xcode=pic32)"
> echo "We attempt to set this to sensible values, but check below to"
> echo "ensure they are OK. If you wish to override any then please use:"
> echo "setenv NAME_OF_ENVIROMENT_VARIABLE value_of_enviroment_variable"
> echo "(if you use tcsh, csh or a similar shell) or"
> echo "NAME_OF_ENVIROMENT_VARIABLE value_of_enviroment_variable"
> echo "export NAME_OF_ENVIROMENT_VARIABLE"
> echo "if you use sh, bash or a similar shell"
> fi
> **
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/0e5b5d21-9dda-492a-b427-ea0d7104505an%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CALZQg1bJDhcp1nvFMoRcgWUb6_9tCEQdoQjQkvr%3DKgHN48ix_Q%40mail.gmail.com.

[sage-devel] Re: Help --> Sage Tutorial, Reference etc doesn't load in JupyterLab

2022-05-25 Thread Kwankyu Lee



On Wednesday, May 25, 2022 at 4:03:52 PM UTC+9 Eric Gourgoulhon wrote:

> Thanks for the report. 
> I confirm the bug with Sage 9.7.beta0 on Ubuntu 20.04.
>

This is not new. At least, Sage 9.5 had the problem.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2405254e-e48a-45ca-b24f-a6e03fceb9c9n%40googlegroups.com.

[sage-devel] Re: Help --> Sage Tutorial, Reference etc doesn't load in JupyterLab

2022-05-25 Thread Eric Gourgoulhon

Thanks for the report. 
I confirm the bug with Sage 9.7.beta0 on Ubuntu 20.04. 

Eric. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/181ffbbd-1e1f-4f51-9158-7e234e7ec938n%40googlegroups.com.

[sage-devel] Virtual Sage Days June 1–3: Preliminary program, Registration

Re: [sage-devel] Re: Run the actual Sage script

Re: [sage-devel] Re: Run the actual Sage script

Re: [sage-devel] [ 1 = 1+0i ] <=> [ 1 = 1 ]

Re: [sage-devel] error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

Re: [sage-devel] error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

[sage-devel] Re: error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

[sage-devel] error in the function modular_decomposition(g) from sage.graphs.graph_decompositions.modular_decomposition

Re: [sage-devel] [ 1 = 1+0i ] <=> [ 1 = 1 ]

[sage-devel] Re: Help --> Sage Tutorial, Reference etc doesn't load in JupyterLab

[sage-devel] Re: Help --> Sage Tutorial, Reference etc doesn't load in JupyterLab

11 matches

Site Navigation

Mail list logo

Footer information