Re: [sage-devel] Help with installing package lrslib-062+autotools-2017-03-03.p1

[Lisa Marie]

thanks, that worked!

zsc...@gmail.com schrieb am Donnerstag, 14. Januar 2021 um 21:56:31 UTC+1:

> Did you build sage from source? I had success getting lrslib to build by 
> running:
>
> CFLAGS=-Wno-implicit-function-declaration make lrslib
>
> if you didn't build from source then you might try
>
> CFLAGS=-Wno-implicit-function-declaration sage -i lrslib
>
>
> On Thursday, January 14, 2021 at 2:01:36 PM UTC-5, Lisa Marie wrote:
>>
>> Hi,
>>
>> thanks for the quick help.
>>
>> I'm not really familiar with compiler flags. Could you specify your 
>> answer a bit? Would be really helpful for me!
>>
>> Regards, Lisa
>>
>> dim...@gmail.com schrieb am Donnerstag, 14. Januar 2021 um 17:38:17 
>> UTC+1:
>>
>>> the problem is that the compiler in XCode 12 has unreasonable 
>>> assumptions about C/C++ code.
>>> This most probably can be fixed by setting appropriate compiler flags. 
>>> See the relevant to XCode   12 and macOS 11 tickets on trac.sagemath.org
>>>
>>>
>>>
>>> On Thu, 14 Jan 2021, 15:38 Lisa Marie,  wrote:
>>>
 Hey everybody,

 I have a problem with installing the 
 package lrslib-062+autotools-2017-03-03.p1 for sage. I work on an Macbook 
 with an Intelprocessor and MacOSX Big Sur, 11.1. I also installed every 
 package recommended for sage. 

 Can you help me fix the problem or at least say what the problem is?

 The log-file of the problem is appended.

 Thanks for helping!
 Lisa

 -- 
 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/c10daea1-d3c7-437c-aef5-43eac70296ddn%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/21435af6-0d37-4b9c-9021-d074803ba0d7n%40googlegroups.com.

Re: [sage-devel] Help with installing package lrslib-062+autotools-2017-03-03.p1

[Zachary Scherr]

Did you build sage from source? I had success getting lrslib to build by 
running:

CFLAGS=-Wno-implicit-function-declaration make lrslib

if you didn't build from source then you might try

CFLAGS=-Wno-implicit-function-declaration sage -i lrslib

On Thursday, January 14, 2021 at 2:01:36 PM UTC-5, Lisa Marie wrote:
>
> Hi,
>
> thanks for the quick help.
>
> I'm not really familiar with compiler flags. Could you specify your answer 
> a bit? Would be really helpful for me!
>
> Regards, Lisa
>
> dim...@gmail.com schrieb am Donnerstag, 14. Januar 2021 um 17:38:17 UTC+1:
>
>> the problem is that the compiler in XCode 12 has unreasonable assumptions 
>> about C/C++ code.
>> This most probably can be fixed by setting appropriate compiler flags. 
>> See the relevant to XCode   12 and macOS 11 tickets on trac.sagemath.org
>>
>>
>>
>> On Thu, 14 Jan 2021, 15:38 Lisa Marie,  wrote:
>>
>>> Hey everybody,
>>>
>>> I have a problem with installing the 
>>> package lrslib-062+autotools-2017-03-03.p1 for sage. I work on an Macbook 
>>> with an Intelprocessor and MacOSX Big Sur, 11.1. I also installed every 
>>> package recommended for sage. 
>>>
>>> Can you help me fix the problem or at least say what the problem is?
>>>
>>> The log-file of the problem is appended.
>>>
>>> Thanks for helping!
>>> Lisa
>>>
>>> -- 
>>> 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/c10daea1-d3c7-437c-aef5-43eac70296ddn%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/edc7c4b5-7108-46ca-906e-d62b5e592b4ao%40googlegroups.com.

Re: [sage-devel] Purpose of SAGE_MACOSX_DEPLOYMENT_TARGET

[Zachary Scherr]

That's a fair point.  I guess it's a bit more relevant at the moment since 
homebrew python is, at least for the time being, no longer suitable and 
system python3 is only 3.8.  So for people who have homebrew python 
installed they can't get python 3.9 in sage 9.3 unless they build from 
source.

In any case, it seems prudent to try to figure out what's going on with 
MACOSX_DEPLOYMENT_TARGET.  I'll try to investigate to the best of my 
ability, but I wonder if the problems that led to setting it to 10.9 ten 
years ago are still relevant today.

On Thursday, January 14, 2021 at 4:44:09 AM UTC-5, Dima Pasechnik wrote:
>
>
>
> On Thu, 14 Jan 2021, 00:52 Zachary Scherr, > 
> wrote:
>
>> I've been trying to help out with getting sage to work properly on Mac, 
>> and I was curious if anyone can explain the purpose of 
>> SAGE_MACOSX_DEPLOYMENT_TARGET to me.
>>
>> I don't know autoconf at all, but I find that if I configure with 
>> --with-system-python3=no
>> then SAGE_MACOSX_DEPLOYMENT_TARGET gets set to "legacy".  This is 
>> presumably because of the lines
>>
>> AS_IF([test x$sage_spkg_install_python3 = xno],
>>   [PYTHON_FOR_VENV="$ac_cv_path_PYTHON3"],
>>   [SAGE_MACOSX_DEPLOYMENT_TARGET=legacy])
>> AC_SUBST([PYTHON_FOR_VENV])
>> AC_SUBST([SAGE_MACOSX_DEPLOYMENT_TARGET])
>>
>> located in build/pkgs/python3/spkg-configure.m4.
>>
>> As far as I can tell, this leads to all sorts of warnings when doctesting 
>> sage. 
>>
>
> I would treat the very idea of not using an already installed python3 as a 
> legacy option.
>
> But yes, the issue is related to the correct setting of 
> MACOSX_DEPLOYMENT_TARGET 
> - something that only Apple itself understands well :-)
>
>
> Specifically, I get lots of warnings like:
>>
>> ld: warning: dylib (/usr/local/lib/libmpfr.dylib) was built for newer 
>> macOS version (10.15) than being linked (10.9)
>> ld: warning: dylib (/usr/local/lib/libgmp.dylib) was built for newer 
>> macOS version (10.15) than being linked (10.9)
>> ld: warning: dylib (/usr/local/lib/libgmpxx.dylib) was built for 
>> newer macOS version (10.15) than being linked (10.9)
>> ld: warning: dylib (/usr/local/lib/libgsl.dylib) was built for newer 
>> macOS version (10.15) than being linked (10.9)
>> ld: warning: dylib (/usr/local/lib/libntl.dylib) was built for newer 
>> macOS version (10.15) than being linked (10.9)
>>
>> now I believe that this is caused by src/bin/sage-env which has the 
>> following code:
>>
>> if [ "$UNAME" = "Darwin" ]; then
>>   export MACOSX_VERSION=`uname -r | awk -F. '{print $1}'`
>>   case "$SAGE_MACOSX_DEPLOYMENT_TARGET" in
>>   legacy)
>> # legacy behavior of the Sage distribution.
>> # set MACOSX_DEPLOYMENT_TARGET -- if set incorrectly, this can
>> # cause lots of random "Abort trap" issues on OSX. see trac
>> # #7095 for an example.
>> if [ $MACOSX_VERSION -ge 14 ]; then
>> # various packages have still have issues with
>> # two digit OS X versions
>> MACOSX_DEPLOYMENT_TARGET=10.9
>> else
>> MACOSX_DEPLOYMENT_TARGET=10.$[$MACOSX_VERSION-4]
>> fi
>> export MACOSX_DEPLOYMENT_TARGET
>> ;;
>>   "")
>> # Do nothing
>> ;;
>>   *)
>> # A fixed version set at configure time.
>> export MACOSX_DEPLOYMENT_TARGET=$SAGE_MACOSX_DEPLOYMENT_TARGET
>> ;;
>>   esac
>>
>> and I'm trying to understand where all of this is coming from.  The trac 
>> ticket this references is 11 years old and so I'm not sure it's an issue 
>> any more.
>>
>> -- 
>> 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-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/19afd68d-be22-4a98-a3e7-c694fc6135a8n%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/858b4e3b-35aa-4ee5-8932-678d9d25e9b3o%40googlegroups.com.

Re: [sage-devel] Help with installing package lrslib-062+autotools-2017-03-03.p1

[Lisa Marie]

Hi,

thanks for the quick help.

I'm not really familiar with compiler flags. Could you specify your answer 
a bit? Would be really helpful for me!

Regards, Lisa

dim...@gmail.com schrieb am Donnerstag, 14. Januar 2021 um 17:38:17 UTC+1:

> the problem is that the compiler in XCode 12 has unreasonable assumptions 
> about C/C++ code.
> This most probably can be fixed by setting appropriate compiler flags. See 
> the relevant to XCode   12 and macOS 11 tickets on trac.sagemath.org
>
>
>
> On Thu, 14 Jan 2021, 15:38 Lisa Marie,  wrote:
>
>> Hey everybody,
>>
>> I have a problem with installing the 
>> package lrslib-062+autotools-2017-03-03.p1 for sage. I work on an Macbook 
>> with an Intelprocessor and MacOSX Big Sur, 11.1. I also installed every 
>> package recommended for sage. 
>>
>> Can you help me fix the problem or at least say what the problem is?
>>
>> The log-file of the problem is appended.
>>
>> Thanks for helping!
>> Lisa
>>
>> -- 
>> 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/c10daea1-d3c7-437c-aef5-43eac70296ddn%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/dd289810-2ab9-4f6e-b387-4f6cebf475e3n%40googlegroups.com.

Re: [sage-devel] Help with installing package lrslib-062+autotools-2017-03-03.p1

[Dima Pasechnik]

the problem is that the compiler in XCode 12 has unreasonable assumptions
about C/C++ code.
This most probably can be fixed by setting appropriate compiler flags. See
the relevant to XCode   12 and macOS 11 tickets on trac.sagemath.org



On Thu, 14 Jan 2021, 15:38 Lisa Marie,  wrote:

> Hey everybody,
>
> I have a problem with installing the
> package lrslib-062+autotools-2017-03-03.p1 for sage. I work on an Macbook
> with an Intelprocessor and MacOSX Big Sur, 11.1. I also installed every
> package recommended for sage.
>
> Can you help me fix the problem or at least say what the problem is?
>
> The log-file of the problem is appended.
>
> Thanks for helping!
> Lisa
>
> --
> 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/c10daea1-d3c7-437c-aef5-43eac70296ddn%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/CAAWYfq0SGt0KRUSUCCbdB-rWBHWQrrwNnmXTmtYAFMCUstn41g%40mail.gmail.com.

[sage-devel] Help with installing package lrslib-062+autotools-2017-03-03.p1

[Lisa Marie]

Hey everybody,

I have a problem with installing the 
package lrslib-062+autotools-2017-03-03.p1 for sage. I work on an Macbook 
with an Intelprocessor and MacOSX Big Sur, 11.1. I also installed every 
package recommended for sage. 

Can you help me fix the problem or at least say what the problem is?

The log-file of the problem is appended.

Thanks for helping!
Lisa

-- 
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/c10daea1-d3c7-437c-aef5-43eac70296ddn%40googlegroups.com.
Found local metadata for lrslib-062+autotools-2017-03-03.p1
Attempting to download package lrslib-062+autotools-2017-03-03.tar.gz from 
mirrors
https://mirror.dogado.de/sage/spkg/upstream/lrslib/lrslib-062+autotools-2017-03-03.tar.gz
[..]
lrslib-062+autotools-2017-03-03.p1

Setting up build directory for lrslib-062+autotools-2017-03-03.p1
Finished extraction
No patch files found in ../patches

Host system:
Darwin Lisa-Maries-MBP.fritz.box 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec  
2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64 x86_64

C compiler: gcc
C compiler version:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1
Apple clang version 12.0.0 (clang-1200.0.32.28)
Target: x86_64-apple-darwin20.2.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Package 'lrslib' is currently not installed
No legacy uninstaller found for 'lrslib'; nothing to do
Configuring lrslib-062+autotools-2017-03-03.p1
configure: WARNING: unrecognized options: --disable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking build system type... x86_64-apple-darwin20.2.0
checking host system type... x86_64-apple-darwin20.2.0
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker 
(/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
 is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 786432
checking how to convert x86_64-apple-darwin20.2.0 file names to 
x86_64-apple-darwin20.2.0 format... func_convert_file_noop
checking how to convert x86_64-apple-darwin20.2.0 file names to toolchain 
format... func_convert_file_noop
checking for 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
 option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking f

Re: [sage-devel] Bug in __hash__ for PermutationGroupElement

[Vincent Delecroix]

Dear Johannes,

Thanks for the report. This is indeed unfortunate. I opened
the following ticket

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

Best
Vincent

Le 14/01/2021 à 11:31, Johannes Schwab a écrit :

Dear all,

the current implementation of __hash__ for PermutationGroupElement returns
a hash that not only depends on the given permutation, but also on the
group the permutation lives in.
Thus the "same" permutation (when compared with __eq__) may have different
hash values, which is not in line with the Python documentation (
https://docs.python.org/3.5/reference/datamodel.html#object.__hash__) and
leads to unexpected situations as the following.

sage: G = SymmetricGroup(2)
sage: H = SymmetricGroup(1)
sage: d = {G.one() : "FooBaa"}
sage: H.one() in list(d.keys())
True
sage: H.one() in d
False

Best,
Johannes Schwab



--
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/984ee527-1a60-37fa-88d0-c00093436266%40gmail.com.

[sage-devel] Bug in __hash__ for PermutationGroupElement

[Johannes Schwab]

Dear all,

the current implementation of __hash__ for PermutationGroupElement returns 
a hash that not only depends on the given permutation, but also on the 
group the permutation lives in.
Thus the "same" permutation (when compared with __eq__) may have different 
hash values, which is not in line with the Python documentation (
https://docs.python.org/3.5/reference/datamodel.html#object.__hash__) and 
leads to unexpected situations as the following.

sage: G = SymmetricGroup(2) 
sage: H = SymmetricGroup(1)
sage: d = {G.one() : "FooBaa"} 
sage: H.one() in list(d.keys())
True 
sage: H.one() in d
False

Best,
Johannes Schwab

-- 
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/66a4796f-19da-42aa-b530-4f7f70402979n%40googlegroups.com.

Re: [sage-devel] Purpose of SAGE_MACOSX_DEPLOYMENT_TARGET

[Dima Pasechnik]

On Thu, 14 Jan 2021, 00:52 Zachary Scherr,  wrote:

> I've been trying to help out with getting sage to work properly on Mac,
> and I was curious if anyone can explain the purpose of
> SAGE_MACOSX_DEPLOYMENT_TARGET to me.
>
> I don't know autoconf at all, but I find that if I configure with
> --with-system-python3=no
> then SAGE_MACOSX_DEPLOYMENT_TARGET gets set to "legacy".  This is
> presumably because of the lines
>
> AS_IF([test x$sage_spkg_install_python3 = xno],
>   [PYTHON_FOR_VENV="$ac_cv_path_PYTHON3"],
>   [SAGE_MACOSX_DEPLOYMENT_TARGET=legacy])
> AC_SUBST([PYTHON_FOR_VENV])
> AC_SUBST([SAGE_MACOSX_DEPLOYMENT_TARGET])
>
> located in build/pkgs/python3/spkg-configure.m4.
>
> As far as I can tell, this leads to all sorts of warnings when doctesting
> sage.
>

I would treat the very idea of not using an already installed python3 as a
legacy option.

But yes, the issue is related to the correct setting of
MACOSX_DEPLOYMENT_TARGET
- something that only Apple itself understands well :-)


Specifically, I get lots of warnings like:
>
> ld: warning: dylib (/usr/local/lib/libmpfr.dylib) was built for newer
> macOS version (10.15) than being linked (10.9)
> ld: warning: dylib (/usr/local/lib/libgmp.dylib) was built for newer
> macOS version (10.15) than being linked (10.9)
> ld: warning: dylib (/usr/local/lib/libgmpxx.dylib) was built for newer
> macOS version (10.15) than being linked (10.9)
> ld: warning: dylib (/usr/local/lib/libgsl.dylib) was built for newer
> macOS version (10.15) than being linked (10.9)
> ld: warning: dylib (/usr/local/lib/libntl.dylib) was built for newer
> macOS version (10.15) than being linked (10.9)
>
> now I believe that this is caused by src/bin/sage-env which has the
> following code:
>
> if [ "$UNAME" = "Darwin" ]; then
>   export MACOSX_VERSION=`uname -r | awk -F. '{print $1}'`
>   case "$SAGE_MACOSX_DEPLOYMENT_TARGET" in
>   legacy)
> # legacy behavior of the Sage distribution.
> # set MACOSX_DEPLOYMENT_TARGET -- if set incorrectly, this can
> # cause lots of random "Abort trap" issues on OSX. see trac
> # #7095 for an example.
> if [ $MACOSX_VERSION -ge 14 ]; then
> # various packages have still have issues with
> # two digit OS X versions
> MACOSX_DEPLOYMENT_TARGET=10.9
> else
> MACOSX_DEPLOYMENT_TARGET=10.$[$MACOSX_VERSION-4]
> fi
> export MACOSX_DEPLOYMENT_TARGET
> ;;
>   "")
> # Do nothing
> ;;
>   *)
> # A fixed version set at configure time.
> export MACOSX_DEPLOYMENT_TARGET=$SAGE_MACOSX_DEPLOYMENT_TARGET
> ;;
>   esac
>
> and I'm trying to understand where all of this is coming from.  The trac
> ticket this references is 11 years old and so I'm not sure it's an issue
> any more.
>
> --
> 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/19afd68d-be22-4a98-a3e7-c694fc6135a8n%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/CAAWYfq1-i6qk_-XfwnvYi%2B%2BP-7jUaWagNqK3tro8KJaH%3DztCUg%40mail.gmail.com.