[sage-devel] Re: The needy #needs directive in doct-tests

[Andrew]

To answer my own question, I just found:

If # optional or # needs is placed right after the sage: prompt, it is a 
block-scoped tag, which applies to all doctest lines until a blank line is 
encountered.

On Monday 19 August 2024 at 1:51:29 pm UTC+10 Andrew wrote:

> I am adding some doc-tests to some code that is currently configured as a 
> package. My tests look like:
>
> EXAMPLES::
>
> sage: X(...)  # needs my_package
> sage: Y(...)  # needs my_package
> sage: Z(...)  # needs my_package
>
> Is there a way to avoid adding # needs my_package to every line?  Ideally, 
> it should be possible to set this once at the beginning of the file, but it 
> would be an improvement if it was only needed once per test-block. 
>
> I thought that there was a recent post about this issue, but I couldn't 
> find it. Sorry if I have missed it.
>
> Andrew
> 
>

-- 
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/ad6f3c91-d4c9-4b47-94c9-4e716e9237fcn%40googlegroups.com.

[sage-devel] The needy #needs directive in doct-tests

[Andrew]

I am adding some doc-tests to some code that is currently configured as a 
package. My tests look like:

EXAMPLES::

sage: X(...)  # needs my_package
sage: Y(...)  # needs my_package
sage: Z(...)  # needs my_package

Is there a way to avoid adding # needs my_package to every line?  Ideally, 
it should be possible to set this once at the beginning of the file, but it 
would be an improvement if it was only needed once per test-block. 

I thought that there was a recent post about this issue, but I couldn't 
find it. Sorry if I have missed it.

Andrew


-- 
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/45d1e1e9-7587-4417-95c5-51a9f05ac453n%40googlegroups.com.

[sage-devel] Re: Voting: Block-scoped optional tag and the keyword

[Andrew]

(B) "requires"

On Thursday, 29 June 2023 at 12:40:07 pm UTC+10 Kwankyu Lee wrote:

> Hi,
>
> We spent six days for the preliminary discussion in the sage-devel thread
>
> https://groups.google.com/g/sage-devel/c/OUnoroIf0qc
>
> about choosing the keyword triggering block-scoped optional tag needed in 
>
> https://github.com/sagemath/sage/issues/35750
>
> We now start the voting with the four candidates (A), (B), (C), (D). The 
> voting will end 7th July 23:59 KST (Korea Standard Time). During the 
> voting, discussions can continue in the linked places but please only your 
> vote (and, if you will, short comment) to this thread.
>
> (A) "needs"
>
> sage: # needs sage.rings.number_field
> sage: QQbar(I)^2
> -1
> sage: QQbar(I)^10 # long time
> 1
>
> sage: # needs sage.rings.finite_rings
> sage: F = GF(7)
> sage: F(1) + QQbar(1)  # needs sage.rings.number_field
> ...
>
> (B) "requires"
>
> sage: # requires sage.rings.number_field
> sage: QQbar(I)^2
> -1
> sage: QQbar(I)^10  # long time
> 1
>
> sage: # requires sage.rings.finite_rings
> sage: F = GF(7)
> sage: F(1) + QQbar(1)  # requires sage.rings.number_field
> ...
>
> (C) "uses"
>
> sage: # uses sage.rings.number_field
> sage: QQbar(I)^2
> -1
> sage: QQbar(I)^10  # long time
> 1
>
> sage: # uses sage.rings.finite_rings
> sage: F = GF(7)
> sage: F(1) + QQbar(1)  # uses sage.rings.number_field
> ...
>
> (D) "standard"
>
> sage: # use standard feature - sage.rings.number_field
> sage: QQbar(I)^2
> -1
> sage: QQbar(I)^10  # long time
> 1
>
> sage: # use standard feature - sage.rings.finite_rings
> sage: F = GF(7)
> sage: F(1) + QQbar(1)  # standard - sage.rings.number_field
> ...
>
> Please just focus on the keyword. Don't worry about minor details or 
> punctuations: the keyword would be recognized, the rest would be ignored 
> noise, in the implementation.
>
> Thanks for your attention. Happy voting :-)
>
>
>
>  
>
>

-- 
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/4fe94f10-25e7-40b8-8994-b785e38808b2n%40googlegroups.com.

[sage-devel] Re: MIgration to GitHub: Heads-up on org invitations

[Andrew]

Thank you for all of your work on this!
Andrew

On Thursday, 2 February 2023 at 10:10:01 am UTC+11 Matthias Koeppe wrote:

> It may take a little bit longer because we've hit the rate limit for org 
> invitation.
>
> On Wednesday, February 1, 2023 at 2:11:37 PM UTC-8 Matthias Koeppe wrote:
>
>> Yes, by email. I think all invitations will have been sent out within the 
>> next 2 hours.
>>
>> On Wednesday, February 1, 2023 at 12:52:25 PM UTC-8 Kwankyu Lee wrote:
>>
>>> Does the invitation come by email? I didn't receive it yet.
>>>
>>> On Thursday, February 2, 2023 at 4:52:10 AM UTC+9 Matthias Koeppe wrote:
>>>
>>>> I am sending out invitations to all Sage contributors with known GitHub 
>>>> accounts to join the sagemath organization (unless they are already a 
>>>> Member).
>>>>
>>>> If you accept the invitation, your contributions to Sage (tickets, 
>>>> comments, ...) will be connected to your GitHub account.
>>>>
>>>> Otherwise, we have to create a placeholder account ("mannequin") for 
>>>> your contribution. Our GitHub migration team contact has assured us that 
>>>> it 
>>>> will be possible to link mannequins to real accounts later; but it is an 
>>>> extra step, so it pays off to respond quickly to the invitation.
>>>>
>>>>
>>>>
>>>>

-- 
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/c2428492-a3dc-4ffe-86f7-02cc5340a41dn%40googlegroups.com.

[sage-devel] Position in computational algebra at the University of Sydney

[Andrew]

This is not a true sage-dev question but I posted this to the gap-forum and 
it may be of interest to some.

The University of Sydney is searching for an Associate Professor or 
Professor in computational algebra, with our aim being to appoint a leading 
expert in this field. The successful applicant will take a leadership role 
in the Computational Algebra group in the School of Mathematics and 
Statistics at The University of Sydney. It is anticipated that they will 
work closely with the Magma group and play a key role in the teaching, 
research, and strategic initiatives of the school. Applications close 
Wednesday 01 March 2023 11:59 PM (Sydney time). 

More details about the appointment can be found at: 

https://usyd.wd3.myworkdayjobs.com/en-US/USYD_EXTERNAL_CAREER_SITE/details/Associate-Professor-Professor-in-Computational-Algebra_0100536-3
 

Regards,

-- 
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/b40a90c7-a5b3-464c-9872-510e48e4092fn%40googlegroups.com.

Re: [sage-devel] ERROR In function "is_prime"

[Andrew]

There does seem to be a problem:

sage: k = 61*2^88+1 ; k
18878585599102049192211644417
sage: k.is_prime()
True
sage: k.factor()
18878585599102049192211644417
sage: k == 61*2^88+1
True
sage: GF(k)
Finite Field of size 18878585599102049192211644417


On Saturday, 2 April 2022 at 6:55:44 pm UTC+11 bea...@gmail.com wrote:

> It seems this number is a prime number and 18878585599102049192211644417 = 
> 61*2^88+1 is not a factorization of the number. Hence, everything is fine. 
> Am I missing something here?
>
> cheers,
> Andry
>
> Le sam. 2 avr. 2022 à 02:33, carlos ortiz  a écrit :
>
>> The number:
>>
>> 18878585599102049192211644417 = 61*2^88+1
>>
>> but in sage:
>>
>> k=ZZ(18878585599102049192211644417)
>>
>> k.is_prime()
>>
>> True
>>
>> k.factor() 
>>
>> 18878585599102049192211644417
>>
>> F = FiniteField(18)
>>
>> raise ValueError("the order of a finite field must be a prime power")
>>
>>
>> Howeve,  
>>
>> F=FiniteField(18878585599102049192211644417)
>>
>> F
>>
>> Finite Field of size 18878585599102049192211644417
>>
>> The above functions generate error for this number 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -- 
>> 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/a919429d-900d-4dbe-9106-52f7ddb84600n%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Andry Nirina Rabenantoandro, PhD.
>
>
>

-- 
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/763afff3-3c26-4302-bd20-9d629ec04396n%40googlegroups.com.

[sage-devel] Re: Cannot compile sage on macosx 12.3

[Andrew]

Great. Thank you. That worked.

On Wednesday, 23 March 2022 at 7:58:36 pm UTC+11 Samuel Lelievre wrote:

> You can download the pythran 0.11.0 source tarball from
>
>   https://pypi.io/packages/source/p/pythran/pythran-0.11.0.tar.gz
>
> (as found in `build/pkgs/pythran/checksums.ini`)
>
> and place it in the `upstream` folder of your Sage installation.
>
> Alternatively, you can use
> ```
> ./configure --enable-download-from-upstream-url
> ```
>
>

-- 
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/651a0448-e018-4e64-85b3-05056f7ab75an%40googlegroups.com.

[sage-devel] Re: Cannot compile sage on macosx 12.3

[Andrew]

Thanks. I'll try that!
Andrew

On Monday, 21 March 2022 at 7:54:19 pm UTC+11 Kwankyu Lee wrote:

> This occurred to me from time to time, I just do "sage -i openblas" and 
> "make" again. 
>
>
>

-- 
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/0d154b35-4daa-4f35-bf64-d0163b584e89n%40googlegroups.com.

[sage-devel] cannot compile sage-9.3 on Fedora Rawhide

[Andrew Lyasoff]

The most relevant part of the log file (attached) is this:

libtool: link: ranlib .libs/libquadmath.a
libtool: link: ( cd ".libs" && rm -f "libquadmath.la" && ln -s 
"../libquadmath.la" "libquadmath.la" )
make[4]: *** [Makefile:995: all] Error 2

Error building gcc-9.2.0

gcc on my system is 
$ gcc --version
gcc (GCC) 11.1.1 20210623 (Red Hat 11.1.1-6)

-- 
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/d604fda0-375c-4b2a-a4fd-74f81c1822cdn%40googlegroups.com.

[sage-devel] support_order in SubmoduleWithBasis

[Andrew]

Sometime recently, possibly because of python3, the required argument 
`support_order` was been added to the class 

`sage.modules.with_basis.subquotient.SubmoduleWithBasis`. 

The documentation says:

  ``support_order`` -- an ordering of the support of ``basis`` expressed in 
``ambient`` given as a list

I have a derived class of `SubmoduleWithBasis` that used to work and I am 
trying to understand what is required here. I am a little surprised that a 
list is expected because it can be expensive to compute indexing sets for 
bases, but perhaps this is deemed acceptable when constructing submodules?

More to the point, can someone tell me what the documentation for 
`support_order` actually means? If the ambient space has indexing set 
{1,2,3} and basis {x1,x2,x3} and my submodule is spanned by {x1+x2} then I 
would think that the support should be {1,2}. Is `support_order` meant to 
tell me what order I should walk through the indexing set when rewriting 
elements of the submodule in terms of its basis? I honestly don't know is 
required except that `support_order` must have an `index` method.

As far as I can see the only place that `support_order` is used is ub the 
method  `_support_key`where it becomes the `key` in a `module_morphism` in 
the `list` method of `SubmoduleWithBasis`.

Andrew
 


-- 
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/83e229a6-23fe-4380-acac-6ed71afeb27cn%40googlegroups.com.

[sage-devel] Re: OS X Big Sur progress report

[Andrew]

Just to confirm, I was able to compile 9.3.beta1 on macosx 10.0.1 running 
xcode 12.2 with homebrew.

The following doctests failed with `make ptestlong`:

sage -t --long --random-seed=0 src/sage/misc/sagedoc.py  # 1 doctest failed
sage -t --long --random-seed=0 src/sage/tests/cmdline.py  # 1 doctest failed
sage -t --long --random-seed=0 src/sage/structure/element.pyx  # 8 doctests 
failed
sage -t --long --random-seed=0 src/sage/misc/sageinspect.py  # 11 doctests 
failed
sage -t --long --random-seed=0 src/sage/functions/other.py  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/misc/cachefunc.pyx  # 6 doctests 
failed
sage -t --long --random-seed=0 src/sage/misc/cython.py  # 10 doctests failed
sage -t --long --random-seed=0 src/sage/graphs/connectivity.pyx  # 2 
doctests failed
sage -t --long --random-seed=0 src/sage/repl/ipython_extension.py  # 1 
doctest failed
sage -t --long --random-seed=0 src/sage/parallel/decorate.py  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/ext/memory_allocator.pxd  # 3 
doctests failed
sage -t --long --random-seed=0 src/sage/ext/memory_allocator.pyx  # 3 
doctests failed
sage -t --long --random-seed=0 src/sage/arith/long.pxd  # 2 doctests failed
sage -t --long --random-seed=0 src/sage/cpython/cython_metaclass.pyx  # 1 
doctest failed
sage -t --long --random-seed=0 src/sage/misc/superseded.py  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/cpython/getattr.pyx  # 2 doctests 
failed
sage -t --long --random-seed=0 src/sage/structure/factory.pyx  # 2 doctests 
failed
sage -t --long --random-seed=0 src/sage/misc/lazy_attribute.pyx  # 1 
doctest failed
sage -t --long --random-seed=0 src/sage/misc/inherit_comparison.pyx  # 1 
doctest failed
sage -t --long --random-seed=0 src/sage/rings/integer_fake.pxd  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/misc/session.pyx  # 1 doctest failed
sage -t --long --random-seed=0 src/sage/docs/instancedoc.pyx  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/repl/preparse.py  # 12 doctests 
failed
sage -t --long --random-seed=0 src/sage/cpython/wrapperdescr.pxd  # 1 
doctest failed
sage -t --long --random-seed=0 src/sage/misc/nested_class.pyx  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/cpython/string.pyx  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/misc/gperftools.py  # 1 doctest 
failed
sage -t --long --random-seed=0 src/sage/rings/tate_algebra_ideal.pyx  # 2 
doctests failed

but the most amusing failure was at the end:

Doctests interrupted: 2791/4216 files tested
--
Total time for all tests: 4482.7 seconds
cpu time: 10717.5 seconds
cumulative wall time: 13159.6 seconds
Traceback (most recent call last):
...
OSError: [Errno 24] Too many open files
make: *** [ptestlong] Error 1

That sage is compiling with the just released version of macosx and the 
latest xcode I think that this is a win.
On Tuesday, 17 November 2020 at 5:11:16 pm UTC+11 Andrew wrote:

> Thanks very much for this Matthias. This is almost certainly my problem -- 
> and I have to confess to user error as this was a hack I put in at one 
> point to get around problems with an xcode update. I have deleted a bunch 
> of spurious links like these and am now recompiling. It has already gotten 
> much further than before. Ih particular, givaro now compiles. So I am 
> optimistic that it will finish now.
>
> Thank you again -- and DIma and John -- for your help!
> Andrew
>
> On Tuesday, 17 November 2020 at 4:16:35 pm UTC+11 Matthias Koeppe wrote:
>
>> According to your log, you seem to have /usr/local/include/stdlib.h 
>> and /usr/local/include/math.h -- which seem to be breaking your giac build. 
>> This seems nonstandard.
>>
>>
>>
>> On Sunday, November 15, 2020 at 9:23:40 PM UTC-8 Andrew wrote:
>>
>>> Thanks for this John. Did you do anything special to compile sage with 
>>> big sur? I just tried:
>>>
>>> make distclean && source .homebrew-build-env && ./configure 
>>> --with-system-gfortran=no --with-system-openblas=no --with-system-gmp=no && 
>>> make
>>>
>>> but the build fails with:
>>>
>>> Error building Sage.
>>>
>>> The following package(s) may have failed to build (not necessarily
>>> during this run of 'make all-start'):
>>>
>>> * package: givaro-4.1.1
>>>   last build time: 16 Nov 14:19
>>>   log file:/usr/local/src/sage/logs/pkgs/givaro-4.1.1.log
>>>   build directory: 
>>> /usr/local/src/sage/local/var/tmp/sage/build/givaro-4.1.1
>>>
>>> This is probably not related to 9.3.beta1 as sage has been failing to 
>>> build, with givaro giving an error, on this laptop since 9.1

[sage-devel] Re: OS X Big Sur progress report

[Andrew]

Thanks very much for this Matthias. This is almost certainly my problem -- 
and I have to confess to user error as this was a hack I put in at one 
point to get around problems with an xcode update. I have deleted a bunch 
of spurious links like these and am now recompiling. It has already gotten 
much further than before. Ih particular, givaro now compiles. So I am 
optimistic that it will finish now.

Thank you again -- and DIma and John -- for your help!
Andrew

On Tuesday, 17 November 2020 at 4:16:35 pm UTC+11 Matthias Koeppe wrote:

> According to your log, you seem to have /usr/local/include/stdlib.h 
> and /usr/local/include/math.h -- which seem to be breaking your giac build. 
> This seems nonstandard.
>
>
>
> On Sunday, November 15, 2020 at 9:23:40 PM UTC-8 Andrew wrote:
>
>> Thanks for this John. Did you do anything special to compile sage with 
>> big sur? I just tried:
>>
>> make distclean && source .homebrew-build-env && ./configure 
>> --with-system-gfortran=no --with-system-openblas=no --with-system-gmp=no && 
>> make
>>
>> but the build fails with:
>>
>> Error building Sage.
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: givaro-4.1.1
>>   last build time: 16 Nov 14:19
>>   log file:/usr/local/src/sage/logs/pkgs/givaro-4.1.1.log
>>   build directory: 
>> /usr/local/src/sage/local/var/tmp/sage/build/givaro-4.1.1
>>
>> This is probably not related to 9.3.beta1 as sage has been failing to 
>> build, with givaro giving an error, on this laptop since 9.1. If anyone has 
>> any ideas as to how I might fix this I'd be grateful. I have tried deleting 
>> all of the homebrew packages and reinstalling. completely removing xcode 
>> and reinstalling, playing with the compilation switches, ... 
>>
>> In case anyone has time to look at this, here is my install.log.gz 
>> <https://www.maths.usyd.edu.au/u/mathas/install.log.gz> file . Here is 
>> my list of brew packages:
>> adns eigen gmp libdvdcss libvpx openexr r tkdiff
>> alluxio ffmpeg gnu-getopt libevent libyaml openjpeg rav1e unbound
>> aom fish  gnu-sed libffi little-cms2 openssl@1.1 readline unrar
>> arbflac gnupg libgcrypt lua opus rsync vtk
>> aspell flint gnutls libgpg-error lz4 p11-kit rtmpdump webkit2png
>> autoconf fontconfig gobject-introspection libheif lzo p7zip rubberband 
>> webp
>> automake freetype gpatch libidn2 macvim pandoc ruby wget
>> bash frei0r graphite2 libksba make pari sass x264
>> bash-completion fribidi gsl liblqr metis pcre sdl2 x265
>> bdw-gc gawk guile libmpc mpfi pcre2 shared-mime-info xmlto
>> boost gcc harfbuzz libogg mpfr perl sip xvid
>> cairo gd hdf5 libomp netcdf pinentry snappy xxhash
>> ceres-solver gdbm icu4c libpng nettle pixman speex xz
>> cimg gettext ilmbase libsamplerate ninja pkg-config sqlite yarn
>> cmake gflags imagemagick libsndfile node poppler srt yasm
>> coreutils ghostscript isl libsoxr npth popt suite-sparse zeromq
>> cscope giflib jpeg libtasn1 nspr ppl swig zlib
>> dart git lame libtiff nss protobuf szip zstd
>> dav1d git-extras leptonica libtool ntl pyqt tbb
>> djvu2pdf git-lfs libass libunistring numpy python@3.8 tesseract
>> djvulibre glib libassuan libusb openblas python@3.9 texinfo
>> docbook glog libbluray libvidstab opencore-amr qpdf the_silver_searcher
>> docbook-xsl glpk libde265 libvorbis opencv qt theora
>> font-firacode-nerd-font gimp  
>>   gitup
>>pdf-images
>>
>> Andrew
>>
>

-- 
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/ce20bb96-025d-4f1c-8a47-685cf83426d6n%40googlegroups.com.

Re: [sage-devel] Re: OS X Big Sur progress report

[Andrew]

Dear Dima and John,

Thanks for your hints. I have tried deleting ntl, flint and arb but I am 
still getting stuck on givaro. I'll try removing some more brew packages 
and see if this helps and report back. The list brew packages recommended 
by configure is:
pandoc ffmpeg imagemagick texinfo ppl
All of these already appear in my list of packages above so, yes, all of 
these are already installed.

Andrew


On Tuesday, 17 November 2020 at 5:19:42 am UTC+11 John H Palmieri wrote:

> In my experience, homebrew's "ntl" package can lead to problems when 
> building Sage, so if possible, try deleting it. I have these packages:
>
> % brew list
> autoconfghcjanssonmpcppl
> automakeghostscriptjpegmpfipython@3.8
> bdw-gcgitlibatomic_opsmpfrpython@3.9
> bisongliblibeventmpirr
> boostglpklibffinautyre2c
> bzip2gmplibidn2ncursesreadline
> cmakegnutlslibmpcnettlesphinx-doc
> curlgpatchlibmpdclientninjasqlite
> doxygengsllibpngopenblassuite-sparse
> fontconfigguilelibtasn1openexrtbb
> freetypehaskell-stacklibtiffopenssl@1.1texinfo
> gccicu4clibtoolp11-kitunbound
> gcc@9ilmbaselibunistringpandocwebp
> gdintltoollibxml2pcrexz
> gdbmislmesonpcre2yasm
> gettextispellmetispkg-configzeromq
>
> Then I really just did "source .homebrew-build-env", "./configure", and 
> "make". I have to admit this is with beta releases of Xcode, but I think 
> the previous beta release should match the official version. (I've done 
> this with beta releases of Xcode 12.2 + corresponding command line tools, 
> and also now with a beta release of Xcode 12.3 + command line tools.) I 
> haven't actually tried with the officially released Xcode 12.2 on Big Sur, 
> but I don't think that would change anything for me.
>
> -- 
> John
>
> On Sunday, November 15, 2020 at 11:39:51 PM UTC-8 dim...@gmail.com wrote:
>
>> On Mon, Nov 16, 2020 at 5:23 AM Andrew  wrote: 
>> > 
>> > Thanks for this John. Did you do anything special to compile sage with 
>> big sur? I just tried: 
>> > 
>> > make distclean && source .homebrew-build-env && ./configure 
>> --with-system-gfortran=no --with-system-openblas=no --with-system-gmp=no && 
>> make 
>> > 
>>
>> this forces Sage to build mpir from source (mpir is basically 
>> unmaintained, as we have a ticket to replace the default MP package on 
>> Sage with 
>> GMP, but it's not merged yet), as well as many more packages in Homebrew. 
>>
>> With homebrew present, there is always a chance there will be a 
>> conflict with Sage libraries you build and the ones 
>> in Homebrew. 
>>
>> Besides, platform-specific tools such as compilers are not guaranteed 
>> to work correctly with OSs they were not tested on, so it's 
>> naive to expect that e.g. gfortran 9.2 will work on macOS 11. 
>>
>> Any reasons for you not to follow the recommendation to install 
>> Homebrew packages we recommend? 
>> (see the output of ./configure) 
>>
>> > but the build fails with: 
>> > 
>> > Error building Sage. 
>> > 
>> > The following package(s) may have failed to build (not necessarily 
>> > during this run of 'make all-start'): 
>> > 
>> > * package: givaro-4.1.1 
>> > last build time: 16 Nov 14:19 
>> > log file: /usr/local/src/sage/logs/pkgs/givaro-4.1.1.log 
>> > build directory: 
>> /usr/local/src/sage/local/var/tmp/sage/build/givaro-4.1.1 
>> > 
>> > This is probably not related to 9.3.beta1 as sage has been failing to 
>> build, with givaro giving an error, on this laptop since 9.1. If anyone has 
>> any ideas as to how I might fix this I'd be grateful. I have tried deleting 
>> all of the homebrew packages and reinstalling. completely removing xcode 
>> and reinstalling, playing with the compilation switches, ... 
>> > 
>> > In case anyone has time to look at this, here is my install.log.gz file 
>> . Here is my list of brew packages: 
>> > adns eigen gmp libdvdcss libvpx openexr r tkdiff 
>> > alluxio ffmpeg gnu-getopt libevent libyaml openjpeg rav1e unbound 
>> > aom fish gnu-sed libffi little-cms2 openssl@

[sage-devel] Re: OS X Big Sur progress report

[Andrew]

Thanks for this John. Did you do anything special to compile sage with big 
sur? I just tried:

make distclean && source .homebrew-build-env && ./configure 
--with-system-gfortran=no --with-system-openblas=no --with-system-gmp=no && 
make

but the build fails with:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: givaro-4.1.1
  last build time: 16 Nov 14:19
  log file:/usr/local/src/sage/logs/pkgs/givaro-4.1.1.log
  build directory: /usr/local/src/sage/local/var/tmp/sage/build/givaro-4.1.1

This is probably not related to 9.3.beta1 as sage has been failing to 
build, with givaro giving an error, on this laptop since 9.1. If anyone has 
any ideas as to how I might fix this I'd be grateful. I have tried deleting 
all of the homebrew packages and reinstalling. completely removing xcode 
and reinstalling, playing with the compilation switches, ... 

In case anyone has time to look at this, here is my install.log.gz 
<https://www.maths.usyd.edu.au/u/mathas/install.log.gz> file . Here is my 
list of brew packages:
adns eigen gmp libdvdcss libvpx openexr r tkdiff
alluxio ffmpeg gnu-getopt libevent libyaml openjpeg rav1e unbound
aom fish  gnu-sed libffi little-cms2 openssl@1.1 readline unrar
arbflac gnupg libgcrypt lua opus rsync vtk
aspell flint gnutls libgpg-error lz4 p11-kit rtmpdump webkit2png
autoconf fontconfig gobject-introspection libheif lzo p7zip rubberband webp
automake freetype gpatch libidn2 macvim pandoc ruby wget
bash frei0r graphite2 libksba make pari sass x264
bash-completion fribidi gsl liblqr metis pcre sdl2 x265
bdw-gc gawk guile libmpc mpfi pcre2 shared-mime-info xmlto
boost gcc harfbuzz libogg mpfr perl sip xvid
cairo gd hdf5 libomp netcdf pinentry snappy xxhash
ceres-solver gdbm icu4c libpng nettle pixman speex xz
cimg gettext ilmbase libsamplerate ninja pkg-config sqlite yarn
cmake gflags imagemagick libsndfile node poppler srt yasm
coreutils ghostscript isl libsoxr npth popt suite-sparse zeromq
cscope giflib jpeg libtasn1 nspr ppl swig zlib
dart git lame libtiff nss protobuf szip zstd
dav1d git-extras leptonica libtool ntl pyqt tbb
djvu2pdf git-lfs libass libunistring numpy python@3.8 tesseract
djvulibre glib libassuan libusb openblas python@3.9 texinfo
docbook glog libbluray libvidstab opencore-amr qpdf the_silver_searcher
docbook-xsl glpk libde265 libvorbis opencv qt theora
font-firacode-nerd-font gimp
gitup      
 pdf-images

Andrew

-- 
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/8c646c22-8ace-4dcc-9358-677d80757fc5n%40googlegroups.com.

[sage-devel] Re: Unable to build ecl-16.1.2.p5 on Ubuntu 20.04 LTS

[Andrew Bernard]

Ah, not so fast. More testing revealed that if you remove the Ubuntu 
package libffi-dev, or perhaps don't install it in the first place a full 
clean compile results.

That's good news.

I would therefore say that Ubuntu 20.04 LTS is a viable platform. This was 
built from the sage-9.0 source tar file from the mirrors.


On Friday, 1 May 2020 15:05:26 UTC+10, Matthias Koeppe wrote:
>
>
>> Sage 9.0 does not build on Ubuntu 20. You will have to try a current 
>> development version.
>>  
>>
> I have added this information to the page 
> https://wiki.sagemath.org/ReleaseTours/sage-9.0 ("Installation FAQ").
>
>

-- 
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/942a877b-d744-48f6-b686-7bfd9d777011%40googlegroups.com.

Re: [sage-devel] Still unable to compile 9.1.beta1 on macos 10.15 (catalina)

[Andrew]

 Hi Dima,

> Why would you want to remove Brew---unless you enjoy building gfortran 
> and gmp from source ? :-) 

I definitely do not want to remove brew but the fact is that I could not 
compile sage while it it was present because of an unidentified conflict. 

Note that I did not say that I removed brew but, instead, that I *renamed* 
the directories to compile sage. Once I sage finished compiling I restored 
the directory names so that brew and sage are both happy now. Next time I 
need to build sage my bash build function will temporarily rename the 
directories again. As I said, when I have some time I will try and track 
work out what was causing my problem but for now this is a good enough work 
around.

I've just transferred the repo with few Brew formulae I wrote to sagemath 
> org: 
>
> https://github.com/sagemath/homebrew-science 
>

I was not able to install some of these formulas earlier, with similar 
compile problems. I can try and reproduce this and post as an issue on your 
repository if you like.

Andrew

-- 
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/1c5b1252-4f55-4573-a10e-ce94c61fc459%40googlegroups.com.

Re: [sage-devel] Still unable to compile 9.1.beta1 on macos 10.15 (catalina)

[Andrew]

Thanks Justin, François and Dima, your comments were helpful. I used to 
quaranteen brew from my sage builds but I stopped doing this because others 
managed to compile sage along side homebrew, and even recommended which 
packages to install, and I was able to do this before macos 10.15. When I 
ran into problems with catalina I tried using brew to uninstall all of the 
homebrew packages, but I don't think that I checked to see if the 
directories in /usr/local were empty, perhaps they weren't.

In any case, after renaming the brew directories in /usr/local 
(specifically the bin, include, lib and opt directories), I can compile 
sage again! :)

When I have some time I will remove brew completely and then add everything 
back in slowly and try to isolate and better understand the problem.
Andrew

On Sunday, 26 January 2020 01:03:19 UTC+1, Justin C. Walker wrote:
>
>
>
> > On Jan 25, 2020, at 15:21 , Andrew > 
> wrote: 
> > 
> > On sage-release Justin C Walker has reported successfully compiled sage 
> 9.1.beta1 on a 2019 MBP, 8-core Core i9 running 10.5.2. 
> > 
> > I am running 10.5.2 on 2016 MBP, 4-core Core i7 and, as previously 
> reported, I whenever I try to compile I get stuck with: 
>
> To echo François, it looks like homebrew and Xcode don’t play well 
> together. 
>
> In my case, I do have Xcode 3.x installed, but I don’t use Homebrew or 
> MacPorts, or any of those package managers. 
>
> Does Homebrew really install “/usr/include”?  That seems to be asking for 
> trouble… 
>
> I don’t have anything to add at this point. 
>
> Justin 
>
> -- 
> Justin C. Walker, Curmudgeon at Large 
> Director 
> Institute for the Enhancement of the Director's Income 
> --- 
> Nobody knows the trouble I've been 
> --- 
>
>
>
>

-- 
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/677e267f-9e10-47b6-8dfa-1cff734edbec%40googlegroups.com.

Re: [sage-devel] Still unable to compile 9.1.beta1 on macos 10.15 (catalina)

[Andrew]

Thanks Justin, François and Dima, your comments were helpful. I used to 
quaranteen brew from my sage builds but I stopped doing this because others 
managed to compile sage along side homebrew, and even recommended which 
packages to install, and I was able to do this before macos 10.15. When I 
ran into problems with catalina I tried using brew to uninstall all of the 
homebrew packages, but I don't think that I checked to see if the 
directories in /usr/local were empty, perhaps they weren't.

In any case, after renaming the brew directories in /usr/local 
(specifically the bib, include, lib and opt directories), I am recompile 
sage again! :)

When I have some time I will remove brew completely and then add everything 
back in slowly and try to isolate and better understand the problem.
Andrew

On Sunday, 26 January 2020 01:03:19 UTC+1, Justin C. Walker wrote:
>
>
>
> > On Jan 25, 2020, at 15:21 , Andrew > 
> wrote: 
> > 
> > On sage-release Justin C Walker has reported successfully compiled sage 
> 9.1.beta1 on a 2019 MBP, 8-core Core i9 running 10.5.2. 
> > 
> > I am running 10.5.2 on 2016 MBP, 4-core Core i7 and, as previously 
> reported, I whenever I try to compile I get stuck with: 
>
> To echo François, it looks like homebrew and Xcode don’t play well 
> together. 
>
> In my case, I do have Xcode 3.x installed, but I don’t use Homebrew or 
> MacPorts, or any of those package managers. 
>
> Does Homebrew really install “/usr/include”?  That seems to be asking for 
> trouble… 
>
> I don’t have anything to add at this point. 
>
> Justin 
>
> -- 
> Justin C. Walker, Curmudgeon at Large 
> Director 
> Institute for the Enhancement of the Director's Income 
> --- 
> Nobody knows the trouble I've been 
> --- 
>
>
>
>

-- 
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/fdb76431-1205-4c28-9ae7-6ee25eae148a%40googlegroups.com.

[sage-devel] Re: OSX Catalina works

[Andrew]

For the time being I have given up on trying to compile sage directly and 
have instead installed it using anaconda.

Andrew

On Tuesday, 5 November 2019 11:54:00 UTC+8, Andrew wrote:
>
> Sadly this still is not working for me. When I found that using your brew 
> formulae didn't work I uninstalled brew, xcode and the command line tools 
> and then reinstalled everything. My current configuration is:
>
> $ sw_vers
> ProductName:Mac OS X
> ProductVersion:10.15.1
> BuildVersion:19B88
>
> $ xcode-select --version
> xcode-select version 2370.
>
> $ xcodebuild -version
> Xcode 11.2
> Build version 11B52
>
> $ brew list
> autoconfgnutls  libmpc  openexrshared-
> mime-info
> automakegpatch  libomp  opensslsqlite
> boost   icu4c   libpng  openssl@1.1texinfo
> cimgilmbase libtasn1p11-kitunbound
> cmake   isl libtool p7zip  unrar
> gcc libde265libunistringpari   xz
> gdbmlibdvdcss   mpfipcre
> gettext libeventmpfrpkg-config
> gliblibffi  nettle  python
> gmp libidn2 ntl readline
>
> $ env
> NVM_RC_VERSION=
> TERM_PROGRAM=Apple_Terminal
> NVM_CD_FLAGS=
> SHELL=/usr/local/bin/bash
> TERM=xterm-256color
> TMPDIR=/var/folders/s0/zb5nzt557xj_hc2t_4j_c2zrgn/T/
> TERM_PROGRAM_VERSION=433
> HTTP_SMS_USER=mathas
> OLDPWD=/Users/andrew
> TERM_SESSION_ID=8B5621BC-E947-4260-A2DD-0ABB88C39133
> NVM_DIR=/Users/andrew/.nvm
> USER=andrew
> TIMEFORMAT=
> real %3Ruser %3Usys %3Spcpu %P
>
> SAGE_BROWSER=chrome
> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.bB0vdzfNg7/Listeners
> SAGE_INSTALL_CCACHE=yes
> PATH=/Users/andrew/bin:/Users/andrew/.node/bin:/usr/local/sbin:/usr/local/
> bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin:/usr/
> local/sbin
> INPUTRC=/Users/andrew/.dotfiles/config/inputrc
> PWD=/usr/local/src/sage
> LANG=en_AU.UTF-8
> SAGE_ROOT=/usr/local/src/sage
> XPC_FLAGS=0x0
> HISTIGNORE=&:bg:fg:ll:h
> XPC_SERVICE_NAME=0
> SHLVL=1
> HOME=/Users/andrew
> MAKE=make -j3
> XDG_CONFIG_HOME=/Users/andrew/.dotfiles/
> TEXEDIT=gvim +%d %s
> PYCURL_CURL_CONFIG=/usr/local/opt/curl-openssl/bin/curl-config
> FULLPATH=/Users/andrew/bin:/Users/andrew/.node/bin:/usr/local/sbin:/usr/
> local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin:
> /usr/local/sbin
> LOGNAME=andrew
> DISPLAY=:0
> SQLITE_EXEMPT_PATH_FROM_VNODE_GUARDS=/Users/andrew/Library/WebKit/
> Databases
> HISTTIMEFORMAT=%H:%M > 
> _=/usr/bin/env
>
>
> Is there anything wrong in my attached config file?
>
> Andrew
>
> ps. I also tried compiling with https://trac.sagemath.org/ticket/28691 
> but the build failed in exactly the same way.
>
> On Monday, 4 November 2019 16:35:55 UTC+11, John H Palmieri wrote:
>>
>> I am using the same versions of OS and Xcode as you. I am now doing this 
>> with a third computer. This one had an old Xcode and some homebrew stuff 
>> already installed, and it gave me some problems. I ended up uninstalling 
>> and then reinstalling various parts of homebrew, and Sage now builds for 
>> me. (I had also first installed some things by hand, like gfortran many 
>> months ago. So I had to delete things like that when doing the homebrew 
>> installation.)
>>
>> $ brew list
>> autoconflibdvdcss   p7zip
>> automakelibeventpari
>> boost   libffi  pcre
>> cabextract  libidn2 pkg-config
>> cimglibmpc  python
>> cmake   libomp  readline
>> emacs-mac   libpng  shared-mime-info
>> gcc libtasn1sqlite
>> gdbmlibtool texinfo
>> gettext libunistringunbound
>> glibmpfiunrar
>> gmp mpfrwine
>> gnutls  nettle  winetricks
>> gpatch  ntl     x265
>> icu4c   openexr xz
>> ilmbase openssl yasm
>> isl openssl@1.1
>> libde265p11-kit
>>
>>
>> $ brew --version
>> Homebrew 2.1.15
>> Homebrew/homebrew-core (git revision d191f; last commit 2019-11-03)
>> Homebrew/homebrew-cask (git revision cbd79; last commit 2019-11-03)
>>
>>
>>
>>
>> On Sunday, November 3, 2019 at 8:53:57 PM UTC-8, Andrew wrote:
>>>
&g

[sage-devel] Re: OSX Catalina works

[Andrew]

Great, thanks John. I have essentially the same version of brew: 
Homebrew 2.1.15
Homebrew/homebrew-core (git revision 89bf3; last commit 2019-11-04)
Homebrew/homebrew-cask (git revision e317e; last commit 2019-11-04)

but I have many more brew packages installed. I reinstalled all of the brew 
packages last week but I have just uninstalled all of the brew packages. I 
will now add everything back in one at a time, starting with things on your 
list, and see if I can compile sage. I'll report back what I find.

Andrew


On Monday, 4 November 2019 16:35:55 UTC+11, John H Palmieri wrote:
>
> I am using the same versions of OS and Xcode as you. I am now doing this 
> with a third computer. This one had an old Xcode and some homebrew stuff 
> already installed, and it gave me some problems. I ended up uninstalling 
> and then reinstalling various parts of homebrew, and Sage now builds for 
> me. (I had also first installed some things by hand, like gfortran many 
> months ago. So I had to delete things like that when doing the homebrew 
> installation.)
>
> $ brew list
> autoconflibdvdcss   p7zip
> automakelibeventpari
> boost   libffi  pcre
> cabextract  libidn2 pkg-config
> cimglibmpc  python
> cmake   libomp  readline
> emacs-mac   libpng  shared-mime-info
> gcc libtasn1sqlite
> gdbmlibtool texinfo
> gettext libunistringunbound
> glibmpfiunrar
> gmp mpfrwine
> gnutls  nettle  winetricks
> gpatch  ntl x265
> icu4c   openexr xz
> ilmbase openssl yasm
> isl openssl@1.1
> libde265p11-kit
>
>
> $ brew --version
> Homebrew 2.1.15
> Homebrew/homebrew-core (git revision d191f; last commit 2019-11-03)
> Homebrew/homebrew-cask (git revision cbd79; last commit 2019-11-03)
>
>
>
>
> On Sunday, November 3, 2019 at 8:53:57 PM UTC-8, Andrew wrote:
>>
>> I uninstalled xcode and brew's gcc and then reinstall them both but I 
>> still the the same failure with givaro.
>> I don't know if this is related, but even though I installed ntl using 
>> brew it is not used when I compile sage as the log file reports:
>>
>> checking NTL/ZZ.h usability... no
>> checking NTL/ZZ.h presence... yes
>> configure: WARNING: NTL/ZZ.h: present but cannot be compiled
>> configure: WARNING: NTL/ZZ.h: check for missing prerequisite headers?
>> configure: WARNING: NTL/ZZ.h: see the Autoconf documentation
>> configure: WARNING: NTL/ZZ.h: section "Present But Cannot Be Compiled"
>> configure: WARNING: NTL/ZZ.h: proceeding with the compiler's result
>> configure: WARNING: ## -- ##
>> configure: WARNING: ## Report this to sage-...@googlegroups.com ##
>> configure: WARNING: ## -- ##
>> checking for NTL/ZZ.h... no
>> checking whether we can link a program using NTL... no
>> checking NTL version >= 10.3... 11.4.1
>> using Sage's ntl SPKG
>> configure: === checking whether to install the flint SPKG ===
>> checking installing mpfr or ntl? ... yes; install flint as well
>> using Sage's flint SPKG
>> configure: === checking whether to install the arb SPKG ===
>> checking installing flint? ... yes; install arb as well
>> configure: === checking whether to install the bzip2 SPKG ===
>>
>> That sage wants compile flint and arb is expected because I try to 
>> install them with brew I get errors like:
>>
>> ==> make
>> Last 15 lines from /Users/andrew/Library/Logs/Homebrew/flint/02.make:
>>   ~~^
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:324:9:
>>  
>> error: no member named 'islessgreater' in the global namespace
>> using ::islessgreater;
>>   ~~^
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:325:9:
>>  
>> error: no member named 'isunordered' in the global namespace
>> using ::isunordered;
>>   ~~^
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:326:9:
>>  
>> error: no member named 'isunordered' in the global namespace
>> using ::isunordered;
>>   ~~^
>> 13 errors generated.
>> make[2]: *** [build/interfaces/NTL-interface.lo] Error 1
>>
>> These are similar to 

[sage-devel] Re: OSX Catalina works

[Andrew]

I uninstalled xcode and brew's gcc and then reinstall them both but I still 
the the same failure with givaro.
I don't know if this is related, but even though I installed ntl using brew 
it is not used when I compile sage as the log file reports:

checking NTL/ZZ.h usability... no
checking NTL/ZZ.h presence... yes
configure: WARNING: NTL/ZZ.h: present but cannot be compiled
configure: WARNING: NTL/ZZ.h: check for missing prerequisite headers?
configure: WARNING: NTL/ZZ.h: see the Autoconf documentation
configure: WARNING: NTL/ZZ.h: section "Present But Cannot Be Compiled"
configure: WARNING: NTL/ZZ.h: proceeding with the compiler's result
configure: WARNING: ## -- ##
configure: WARNING: ## Report this to sage-devel@googlegroups.com ##
configure: WARNING: ## -- ##
checking for NTL/ZZ.h... no
checking whether we can link a program using NTL... no
checking NTL version >= 10.3... 11.4.1
using Sage's ntl SPKG
configure: === checking whether to install the flint SPKG ===
checking installing mpfr or ntl? ... yes; install flint as well
using Sage's flint SPKG
configure: === checking whether to install the arb SPKG ===
checking installing flint? ... yes; install arb as well
configure: === checking whether to install the bzip2 SPKG ===

That sage wants compile flint and arb is expected because I try to install 
them with brew I get errors like:

==> make
Last 15 lines from /Users/andrew/Library/Logs/Homebrew/flint/02.make:
  ~~^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:324:9:
 
error: no member named 'islessgreater' in the global namespace
using ::islessgreater;
  ~~^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:325:9:
 
error: no member named 'isunordered' in the global namespace
using ::isunordered;
  ~~^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:326:9:
 
error: no member named 'isunordered' in the global namespace
using ::isunordered;
  ~~^
13 errors generated.
make[2]: *** [build/interfaces/NTL-interface.lo] Error 1

These are similar to the errors that I get with givaro when compiling sage.

John: what version of xcode and the command line tools are using and if you 
first do

make distclean

are you still able to compile sage? As I reinstalled xcode from the 
appsrtore I am using the latest versions av I am using:

ProductName:Mac OS X
ProductVersion:    10.15.1
BuildVersion:19B88
Xcode 11.2
Build version 11B52

Andrew




On Saturday, 2 November 2019 05:45:08 UTC+11, Andrew wrote:
>
> Thanks John. I'll give this a try on Monday.
> Andrew
>
> On Saturday, 2 November 2019 04:20:08 UTC+11, John H Palmieri wrote:
>>
>> I just upgraded a different machine to Catalina. This one didn't have 
>> Xcode or homebrew installed beforehand, so I installed Xcode, its 
>> command-line tools, and homebrew's gcc. Then I built Sage and it worked. I 
>> have now installed a bunch of other homebrew packages relevant to Sage, and 
>> the build is going fine. (I had to log out of the machine, so I had to 
>> interrupt the build, but it had made it past givaro and ntl, which were 
>> sticking points for another user in this thread.)
>>
>> Thinking back on the other machine I upgraded, that one was also 
>> relatively "clean": no old Xcode or old homebrew stuff. So for those who 
>> are having problems, I wonder if uninstalling Xcode first would help. Maybe 
>> there are some other old libraries which should be removed before 
>> installing the new Xcode.
>>
>>   John
>>
>>
>> On Monday, October 14, 2019 at 10:43:09 AM UTC-7, Volker Braun wrote:
>>>
>>> Means: I successfully compiled Sage 8.9 on OSX Catalina with Xcode 11.0 
>>>
>>>
>>>
>>> On Sunday, October 13, 2019 at 9:24:44 PM UTC+2, Samuel Lelievre wrote:
>>>>
>>>> Sun 2019-10-13 08:26:52 UTC, Volker Braun:
>>>>>
>>>>> I just upgraded the OSX buildbot and Sage works
>>>>>
>>>> in case anybody is wondering. This is the first time in years
>>>>>
>>>> that the latest OSX release doesn't introduce major toolchain
>>>>>
>>>> issues and/or scrambles the filesystem, hope this starts a trend ;-) 
>>>>>
>>>>
>>>> That's good to hear, and there were people wondering.
>>>> See for instance this question on Ask Sage about SageMath
>>>> and macOS 10.15 "Catalina":
>>

[sage-devel] Re: OSX Catalina works

[Andrew]

Thanks John. I'll give this a try on Monday.
Andrew

On Saturday, 2 November 2019 04:20:08 UTC+11, John H Palmieri wrote:
>
> I just upgraded a different machine to Catalina. This one didn't have 
> Xcode or homebrew installed beforehand, so I installed Xcode, its 
> command-line tools, and homebrew's gcc. Then I built Sage and it worked. I 
> have now installed a bunch of other homebrew packages relevant to Sage, and 
> the build is going fine. (I had to log out of the machine, so I had to 
> interrupt the build, but it had made it past givaro and ntl, which were 
> sticking points for another user in this thread.)
>
> Thinking back on the other machine I upgraded, that one was also 
> relatively "clean": no old Xcode or old homebrew stuff. So for those who 
> are having problems, I wonder if uninstalling Xcode first would help. Maybe 
> there are some other old libraries which should be removed before 
> installing the new Xcode.
>
>   John
>
>
> On Monday, October 14, 2019 at 10:43:09 AM UTC-7, Volker Braun wrote:
>>
>> Means: I successfully compiled Sage 8.9 on OSX Catalina with Xcode 11.0 
>>
>>
>>
>> On Sunday, October 13, 2019 at 9:24:44 PM UTC+2, Samuel Lelievre wrote:
>>>
>>> Sun 2019-10-13 08:26:52 UTC, Volker Braun:
>>>>
>>>> I just upgraded the OSX buildbot and Sage works
>>>>
>>> in case anybody is wondering. This is the first time in years
>>>>
>>> that the latest OSX release doesn't introduce major toolchain
>>>>
>>> issues and/or scrambles the filesystem, hope this starts a trend ;-) 
>>>>
>>>
>>> That's good to hear, and there were people wondering.
>>> See for instance this question on Ask Sage about SageMath
>>> and macOS 10.15 "Catalina":
>>>
>>> - How to unlock SageMath 8.8 on macOS 10.15 Catalina?
>>>   https://ask.sagemath.org/question/48293
>>>
>>> By "Sage works" do you mean any of the following?
>>>
>>> - there are / there will be binaries for macOS 10.15 "Catalina"
>>> - the SageMath 8.9 binaries for macOS 10.14 "Mojave"
>>>   also work for macOS 10.15 "Catalina"
>>> - on macOS 10.15 "Catalina" building SageMath 8.9 from
>>>   source gives a version that works and is not "locked"
>>>
>>>
>>>

-- 
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/e692024e-8d96-4468-9457-de523740db9c%40googlegroups.com.

Re: [sage-devel] Re: OSX Catalina works

[Andrew]

On Wednesday, 30 October 2019 23:27:45 UTC+11, Dima Pasechnik wrote:
>
> I meant cmath files without extensions. These are C++ header files.
> It appears there are two such files on the list. Are they different?
>
> In the interim have have installed homebrew's gcc to see if this helps, 
but it doesn't. The cmath files that I now have on my system are:

-rw-r--r--  1 rootwheel  14515 23 Jul 03:08 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath
-rw-r--r--  1 rootwheel  14515 23 Jul 03:08 
/Library/Developer/CommandLineTools/usr/include/c++/v1/cmath

As you suspected, these two files are identical.

from homebrew's gcc:
-rw-r--r--  1 andrew  staff619 14 Aug 22:29 
/usr/local/Cellar/boost/1.71.0/include/boost/compatibility/cpp_c_headers/cmath
-rw-r--r--  1 andrew  staff  49094 12 Aug 17:58 
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/cmath
-rw-r--r--  1 andrew  staff   6570 12 Aug 17:58 
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/ext/cmath
-rw-r--r--  1 andrew  staff  43806 12 Aug 17:58 
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/tr1/cmath
-rw-r--r--  1 andrew  wheel619 31 Oct 13:51 
/usr/local/src/sage/local/include/boost/compatibility/cpp_c_headers/cmath

Andrew

-- 
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/b6bdc28e-97d6-44b1-bd2c-f86bd1054c0f%40googlegroups.com.

Re: [sage-devel] Re: OSX Catalina works

[Andrew]

I don't have anything like MACOSX_DEPLOYMENT_TARGET or CPLUS_INCLUDE_PATH 
set and I'll paste the list of filenames contain cmath below.

I wonder if this is part of the problem. According to gcc--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 11.0.0 (clang-1100.0.33.8)
Target: x86_64-apple-darwin19.0.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

however, the gxx-include directory 

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1

does not exist. I tried adding a link from here to 

/Library/Developer/CommandLineTools/usr/include/c++/v1/

and setting CXXFLAGS="-isysroot 
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk" but this didn't help.

Thanks again for your help!
Andrew

/Applications/GIMP.app/Contents/Resources/lib/python2.7/lib-dynload/cmath.so
/Applications/Xcode.app/Contents/Developer/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/lib-dynload/cmath.cpython-37m-darwin.so
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/cmath.rb
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/cmath
/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/lib-dynload/cmath.cpython-37m-darwin.so
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/cmath.rb
/Library/Developer/CommandLineTools/usr/include/c++/v1/cmath
/Library/Ruby/Gems/2.6.0/specifications/default/cmath-1.0.0.gemspec
/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cmath.so
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/cmath.rb
/System/Library/Templates/Data/Library/Ruby/Gems/2.6.0/specifications/default/cmath-1.0.0.gemspec
/opt/metasploit-framework/embedded/lib/ruby/2.4.0/cmath.rb
/usr/local/Cellar/boost/1.71.0/include/boost/compatibility/cpp_c_headers/cmath
/usr/local/Cellar/boost/1.71.0/include/boost/config/no_tr1/cmath.hpp
/usr/local/Cellar/boost/1.71.0/include/boost/phoenix/stl/cmath.hpp
/usr/local/Cellar/boost/1.71.0/include/boost/units/cmath.hpp
/usr/local/Cellar/ipython/7.8.0/libexec/vendor/lib/python3.7/site-packages/jedi/third_party/typeshed/stdlib/2and3/cmath.pyi
/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/lib-dynload/cmath.cpython-37m-darwin.so
/usr/local/Cellar/python@2/2.7.16_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cmath.so
/usr/local/Cellar/ruby/2.6.5/lib/ruby/2.6.0/cmath.rb
/usr/local/Cellar/ruby/2.6.5/lib/ruby/gems/2.6.0/specifications/default/cmath-1.0.0.gemspec
/usr/local/src/sage/local/include/boost/compatibility/cpp_c_headers/cmath
/usr/local/src/sage/local/include/boost/config/no_tr1/cmath.hpp
/usr/local/src/sage/local/include/boost/phoenix/stl/cmath.hpp
/usr/local/src/sage/local/include/boost/units/cmath.hpp

On Wednesday, 30 October 2019 17:41:33 UTC+11, Dima Pasechnik wrote:
>
> it seems to be related to Apple removing support for libstdc++. 
>
> Could it be that you have something related to "deployment target" 
> (MACOSX_DEPLOYMENT_TARGET ?) in your default environment variables, or 
> similar settings in Xcode? 
> Or perhaps CPLUS_INCLUDE_PATH is set somewhere? 
>
> Perhaps your "XcodeDefault.xctoolchain" - that's where that wretched 
> C++ cmath header comes from - is pointing to a wrong toolchain? 
> Can you search for the files named "cmath" on the machine? 
>

-- 
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/518a5813-7c1d-4d5d-85df-bf43398aef7c%40googlegroups.com.

Re: [sage-devel] Re: OSX Catalina works

[Andrew]

Thanks everyone for their comments.

 > try explicitly adding "-stdlib=libc++" to CXXLAGS and LDFLAGS.

Adding these flags to the Makefile didn't change anything: the build again 
failed with givaro-4.1.1

> After installing Xcode, did you run Xcode? 

Yes, of course! Xcode and the command line tools are both fully installed, 
with the terms and conditions agreed. The build would fail much earlier if 
this was not the case.

Just for fun I tried reinstalling Xcode (and the command line tools and 
then accepting the xcode conditions etc) but this made no difference in the 
sense that the sage build died at exactly the same place. Perhaps I should 
winding back to xcode 11?

Andrew

On Wednesday, 30 October 2019 11:39:18 UTC+11, Samuel Lelievre wrote:
>
> Tue 2019-10-29 11:46 UTC, Andrew: 
> > 
> > Thanks Dima 
> > 
> > On Tuesday, 29 October 2019 17:51:02 UTC+11, Dima Pasechnik wrote: 
> >> 
> >> Did you  run 
> >> 
> >> xcode-select --install 
> >> 
> >> after Xcode upgrade? 
> > 
> > 
> > Yes, the command line tools are correctly installed but, as far as I can 
> see, 
> > xcode-select --install  is no longer the correct way to check this 
> > because it results in the error: 
> > 
> > xcode-select: error: command line tools are already installed, use 
> "Software Update" to install updates 
>
> It's still the correct way; the error message is for trying to install 
> while it's already installed. Sometimes one needs to start XCode 
> once, and agree to the terms and conditions. 
>

-- 
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/5844078d-ed2a-40cc-ac52-30d92718fe1d%40googlegroups.com.

Re: [sage-devel] Re: OSX Catalina works

[Andrew]

Thanks Dima

On Tuesday, 29 October 2019 17:51:02 UTC+11, Dima Pasechnik wrote:
>
> Did you  run 
>
> xcode-select --install 
>
> after Xcode upgrade? 
>

Yes, the command line tools are correctly installed but, as far as I can 
see, xcode-select --install  is no longer the correct way to check this 
because it results in the error:

xcode-select: error: command line tools are already installed, use 
"Software Update" to install updates
 

> By the way, why don't you use NTL from brew? 
> https://formulae.brew.sh/formula/ntl#default 
>
> you can also make things easier by installing Flint and Arb into 
> homebrew, by using formulas from 
> https://github.com/dimpase/homebrew-science 
>
> Run 
>
> brew install dimpase/science/flint 
> brew install dimpase/science/arb 
>

Thanks. I didn't know that there were homebrew formulas for any of these. 
Unfortunately, neither of these work either, giving similar (but shorter) 
messages to the compilation errors with sage. Installing flint results in:

==> Downloading http://flintlib.org/flint-2.5.2.tar.gz
 
100.0%
==> ./configure --prefix=/usr/local/Cellar/flint/2.5.2_1 
--with-gmp=/usr/local/opt/gmp --with-mpfr=/u
==> make
Last 15 lines from /Users/andrew/Library/Logs/Homebrew/flint/02.make:
  ~~^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:324:9:
 
error: no member named 'islessgreater' in the global namespace
using ::islessgreater;
  ~~^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:325:9:
 
error: no member named 'isunordered' in the global namespace
using ::isunordered;
  ~~^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/cmath:326:9:
 
error: no member named 'isunordered' in the global namespace
using ::isunordered;
  ~~^
13 errors generated.
make[2]: *** [build/interfaces/NTL-interface.lo] Error 1
clang: error: no such file or directory: 'build/interfaces/NTL-interface.lo'
make[1]: *** [libflint-13.5.2.dylib] Error 1
make: *** [library] Error 2


and arb fails in the same way because it first tries to install flint.

Andrew



> (these are source-only, so this will build packages from source) 
>
>
> On Tue, Oct 29, 2019 at 2:01 AM Andrew > 
> wrote: 
> > 
> > I (stupidly) upgraded to XCode 11.1 on catalina. I have succeeded in 
> compiling sage with python2, not python 3, on an imac but can't get it to 
> compile on a macbook pro with fairly similar specs.I am using homebrew and 
> have: 
> > 
> > ProductName:Mac OS X 
> > ProductVersion:10.15 
> > BuildVersion:19A603 
> > Xcode 11.1 
> > Build version 11A1027 
> > 
> > with gcc --version returning 
> > 
> > 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 11.0.0 (clang-1100.0.33.8) 
> > Target: x86_64-apple-darwin19.0.0 
> > Thread model: posix 
> > InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>  
>
> > 
> > When I try to compile sage is breaks with: 
> > 
> > * package: givaro-4.1.1 
> >   log file: /usr/local/src/sage/logs/pkgs/givaro-4.1.1.log 
> >   build directory: 
> /usr/local/src/sage/local/var/tmp/sage/build/givaro-4.1.1 
> > * package: ntl-11.3.2 
> >   log file: /usr/local/src/sage/logs/pkgs/ntl-11.3.2.log 
> >   build directory: 
> /usr/local/src/sage/local/var/tmp/sage/build/ntl-11.3.2 
> > 
> > Sometimes I also get ntl failing to compile. I have compared the log 
> files one the two machines but can't identify the problem. I attach the log 
> files for givaro and ntl and the install.log from the machine that has the 
> problem. Does anyone have any ideas how to fix this? 
> > 
> > Andrew 
> > 
> > -- 
> > 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/695c9caa-6efe-49ad-a05f-100c49be7a93%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/dcb00e7a-bd6f-4703-bfbb-e06c040d063d%40googlegroups.com.

[sage-devel] Re: python3 status report (mi-april of last python2 year)

[Andrew]

See https://trac.sagemath.org/ticket/27710 for a python3 fix to 
combinat/tutorial.py

On Sunday, 21 April 2019 09:26:11 UTC+10, Andrew wrote:
>
> Fixing this problem properly as Martin or Volker suggests is probably the 
> best option but `# random print order` is a good option too, which I was 
> not aware of -- or is this really `# random` with additional explanation?
>
> Is there a complete list of the doc-test modifiers anywhere? I just looked 
> and couldn't find one.I guess that I could just grep through all of the 
> documentation...
>
> Andrew
>
> On Saturday, 20 April 2019 12:14:53 UTC+10, Nils Bruin wrote:
>>
>> On Friday, April 19, 2019 at 5:25:13 PM UTC-7, John H Palmieri wrote:
>>>
>>> What does
>>>
>>> sage: C
>>> Set partitions of {'a', 'c', 'b'}
>>>
>>>
>>> reveal? Is it helpful, or can it be omitted?
>>>
>>> Adding to that: perhaps it reveals something for the documentation 
>> reader. But in that case the output doesn't need to be tested. The test 
>> comes later by showing that further methods on C have the desired effect. 
>> In that case,
>>
>> sage: C # random print order
>> Set partitions of {'a', 'c', 'b'}
>> sage: C.cardinality()
>> 5
>>
>> does the trick AND we keep the output displayed for documentation 
>> purposes.
>>
>>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: python3 status report (mi-april of last python2 year)

[Andrew]

Fixing this problem properly as Martin or Volker suggests is probably the 
best option but `# random print order` is a good option too, which I was 
not aware of -- or is this really `# random` with additional explanation?

Is there a complete list of the doc-test modifiers anywhere? I just looked 
and couldn't find one.I guess that I could just grep through all of the 
documentation...

Andrew

On Saturday, 20 April 2019 12:14:53 UTC+10, Nils Bruin wrote:
>
> On Friday, April 19, 2019 at 5:25:13 PM UTC-7, John H Palmieri wrote:
>>
>> What does
>>
>> sage: C
>> Set partitions of {'a', 'c', 'b'}
>>
>>
>> reveal? Is it helpful, or can it be omitted?
>>
>> Adding to that: perhaps it reveals something for the documentation 
> reader. But in that case the output doesn't need to be tested. The test 
> comes later by showing that further methods on C have the desired effect. 
> In that case,
>
> sage: C # random print order
> Set partitions of {'a', 'c', 'b'}
> sage: C.cardinality()
> 5
>
> does the trick AND we keep the output displayed for documentation purposes.
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: python3 status report (mi-april of last python2 year)

[Andrew]

What the accepted best practice for fixing the failing python3 doc-tests? 
For example, in `combinat/tutorial.py` I can fix one of the failing 
doc-tests with:

sage: C = SetPartitions(["a", "b", "c"])
sage: C #py2
Set partitions of {'a', 'c', 'b'}
sage: C #py3
Set partitions of {'a', 'b', 'c'}

but this does not address the underlying problem. At first sight this looks 
like an issue with `SetPartitions` and, indeed, `combinat/setpartition.py` 
has several failing doc-tests but as far as I can see this is actually an 
issue with `Set` even though `sets/set.py` passes all doc-tests. You can 
see this because 

Set(['a', 'b', 'c'])

gives different output with each sage session, at least when `sage` is 
compiled with python3.

On Monday, 15 April 2019 21:56:54 UTC+10, Frédéric Chapoton wrote:
>
> Hello,
>
> sage-with-python3 (now using python 3.7.3) has now *less than 100 files* 
> (94 precisely) with failing doctests, for a total of *324 failing 
> doctests*. Among these, 34 files have a single failing doctest.
>
> A detailed summary can be found here : 
> https://trac.sagemath.org/ticket/26212
>
> There remains many hard-to-fix issues. Please help if you can.
>
> * Matroid, dynamics and combinat people should care for their code. The 
> cluster code needs particular work.
>
> * We should also strive to make all tests pass in rings/
>
> * An expert is required on src/sage/misc/classcall_metaclass.pyx
>
> Frédéric
>
>
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] OSX: pip build failure. zlib dependancy ?

[Andrew]

Although I have not had this problem myself, zlib seems to be an issue for 
some macs. For zlib, John H Palmieri recommends: 

./sage -f zlib python2 python3 && make

Presumably, you have already installed the system headers using something 
like:

open /Library/Developer/CommandLineTools/Packages/
macOS_SDK_headers_for_macOS_10.14.pkg 




On Thursday, 7 March 2019 20:24:17 UTC+11, Vincent Klein wrote:
>
> Ok. Thank you for your answer.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

Thanks. I agree that the obvious solution.  Samuel Lelièvre has supplied 
the patch and, for completeness, I have checked that it fixes the issue by 
recompiling and given a positive review.
Andrew

On Tuesday, 26 February 2019 23:08:07 UTC+11, E. Madison Bray wrote:
>
> Hi Andrew, 
>
> On Tue, Feb 26, 2019 at 12:31 AM Andrew > 
> wrote: 
> > 
> > Thanks very much for this Erik! It's the height of the grant writing 
> season in the antipodeans so I have only just gotten back to this but you 
> told how to troubleshoot and hence fix my problem, which turned out to be 
> annoyingly trivial. 
> > 
> > The reason that sage would not compile for me comes down to the line: 
> > 
> > export PYTHONPATH=`cd src && pwd` 
> > 
> > in the pip spkg-install file. For me this was producing 
> > 
> > > echo $PYTHONPATH 
> > /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src/src 
> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src/src 
> > 
> > Note the space separated repeated path. As a result both python 2 and 3 
> were unable to find pip, which the build process had already successfully 
> built and installed. 
> > 
> > Eventually I tracked this down to my use of CDPATH in my bash shell, 
> which causes the directory name to be echoed when I change directory. If I 
> unset this and compile sage then all is fine. 
> > 
> > I don't know if this constitutes a bug in the spkg-install file or a 
> random idiosyncracy of my setup. I'm happy to file a patch if people think 
> it is the former or to modify my build process if the latter. (As I am able 
> to compile sage again I am happy and don't really care either way). 
>
> Thank you for debugging this and for your analysis.  I would agree 
> this is a bug.  I opened a ticket for it here: 
>
> https://trac.sagemath.org/ticket/27362 
>
> I haven't attached a patch yet so feel free to do so if you want (I 
> already suggested a solution in the ticket description). 
>
>
> > Thanks again to everyone for their help. 
> > Andrew 
> > 
> > ps Dima mentioned making sage compatible with brew. Personally I'd 
> prefer this:) 
> > 
> > On Wednesday, 20 February 2019 00:04:11 UTC+11, E. Madison Bray wrote: 
> >> 
> >> On Tue, Feb 19, 2019 at 9:18 AM Dima Pasechnik  
> wrote: 
> >> > 
> >> > On Mon, Feb 18, 2019 at 11:37 PM John H Palmieri  
> wrote: 
> >> > > 
> >> > > On one of my machines running OS X Mojave, when I run 'make', the 
> pip installation fails, saying 
> >> > > 
> >> > > ModuleNotFoundError: No module named 'zlib' 
> >> > > 
> >> > > That's when the solution is 
> >> > > 
> >> > > ./sage -f zlib python2 python3 
> >> > > make 
> >> > > 
> >> > so this points at inability of Pythons to use system's zlib module on 
> >> > Mojave, even though it's apparently 
> >> > perfectly functional... 
> >> > 
> >> > internet says one should run 
> >> > 
> >> > xcode-select --install 
> >> > sudo installer -pkg 
> >> > 
> /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
>  
>
> >> > -target / 
> >> > 
> >> > to make the headers available. 
> >> > (cf e.g. https://github.com/pyenv/pyenv/issues/1219) 
> >> > 
> >> > Are you saying this particular strain of tsores known as OSX 10.14 is 
> >> > resistant to these spells on this particular box? 
> >> > 
> >> > I think we really should look into using Homebrew for building on 
> OSX, 
> >> > otherwise we are doomed to repeat what's done there... 
> >> 
> >> Personally I would suggest not developing software that isn't built 
> >> for Apple products with Apple's toolchain on an Apple OS, because 
> >> Apple is increasingly hostile to anyone who might have a desire to do 
> >> so. 
> >> 
> >> Even Microsoft cares more (much more) these days about giving the 
> >> developer community what they want and not actively trying to make 
> >> their lives harder. 
> >> 
> >> 
> >> > > On Monday, February 18, 2019 at 12:58:19 PM UTC-8, John H Palmieri 
> wrote: 
> >> > >> 
> >> > >> At this point you should probably do 'make distclean' and start 
> again. There should be no need to do 'sage --sh&#

Re: [sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

Thanks very much for this Erik! It's the height of the grant writing season 
in the antipodeans so I have only just gotten back to this but you told how 
to troubleshoot and hence fix my problem, which turned out to be annoyingly 
trivial. 

The reason that sage would not compile for me comes down to the line:

export PYTHONPATH=`cd src && pwd` 

in the pip spkg-install file. For me this was producing

> echo $PYTHONPATH
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src/src /usr/local/src
/sage/local/var/tmp/sage/build/pip-18.1/src/src 

Note the space separated repeated path. As a result both python 2 and 3 
were unable to find pip, which the build process had already successfully 
built and installed.

Eventually I tracked this down to my use of CDPATH in my bash shell, which 
causes the directory name to be echoed when I change directory. If I unset 
this and compile sage then all is fine.

I don't know if this constitutes a bug in the spkg-install file or a random 
idiosyncracy of my setup. I'm happy to file a patch if people think it is 
the former or to modify my build process if the latter. (As I am able to 
compile sage again I am happy and don't really care either way).

Thanks again to everyone for their help.
Andrew

ps Dima mentioned making sage compatible with brew. Personally I'd prefer 
this:)

On Wednesday, 20 February 2019 00:04:11 UTC+11, E. Madison Bray wrote:
>
> On Tue, Feb 19, 2019 at 9:18 AM Dima Pasechnik  > wrote: 
> > 
> > On Mon, Feb 18, 2019 at 11:37 PM John H Palmieri  > wrote: 
> > > 
> > > On one of my machines running OS X Mojave, when I run 'make', the pip 
> installation fails, saying 
> > > 
> > > ModuleNotFoundError: No module named 'zlib' 
> > > 
> > > That's when the solution is 
> > > 
> > > ./sage -f zlib python2 python3 
> > > make 
> > > 
> > so this points at inability of Pythons to use system's zlib module on 
> > Mojave, even though it's apparently 
> > perfectly functional... 
> > 
> > internet says one should run 
> > 
> > xcode-select --install 
> > sudo installer -pkg 
> > 
> /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
>  
>
> > -target / 
> > 
> > to make the headers available. 
> > (cf e.g. https://github.com/pyenv/pyenv/issues/1219) 
> > 
> > Are you saying this particular strain of tsores known as OSX 10.14 is 
> > resistant to these spells on this particular box? 
> > 
> > I think we really should look into using Homebrew for building on OSX, 
> > otherwise we are doomed to repeat what's done there... 
>
> Personally I would suggest not developing software that isn't built 
> for Apple products with Apple's toolchain on an Apple OS, because 
> Apple is increasingly hostile to anyone who might have a desire to do 
> so. 
>
> Even Microsoft cares more (much more) these days about giving the 
> developer community what they want and not actively trying to make 
> their lives harder. 
>
>
> > > On Monday, February 18, 2019 at 12:58:19 PM UTC-8, John H Palmieri 
> wrote: 
> > >> 
> > >> At this point you should probably do 'make distclean' and start 
> again. There should be no need to do 'sage --sh' and easy_install, and that 
> could easily mess things up. 
> > >> 
> > >> 
> > >> 
> > >> On Monday, February 18, 2019 at 12:29:20 PM UTC-8, Andrew wrote: 
> > >>> 
> > >>> 
> > >>> 
> > >>> On Tuesday, 19 February 2019 03:44:02 UTC+11, John H Palmieri wrote: 
> > >>>> 
> > >>>> Can you post the end of the file logs/pkgs/pip-18.1.log? The last 
> 30 lines or so? Or post the whole file if you can. 
> > >>>> 
> > >>> The log from after the failed make is s below. It says that 
> > >>> No record that 'pip' was ever installed; skipping uninstall 
> > >>> I've tried going into the sage sh and using easy_install 2-7 and 3.6 
> to install pip (as in 
> https://groups.google.com/forum/#!topic/sage-release/XUYlh2DHP9E) and 
> then running make but, again, I end up with pip-18.1 not installed. The 
> problem seems to be that I have pip-19.0.2: 
> > >>> 
> > >>> local/bin/pip --version 
> > >>> pip 19.0.2 from 
> /usr/local/src/sage/local/lib/python2.7/site-packages/pip-19.0.2-py2.7.egg/pip
>  
> (python 2.7) 
> > >>> 
> > >>> install log for pip 
> > >>> 
> > >&g

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

Do you mean that after installing Mojave you never again managed
> to compile Sage? Do you still have a working version of Sage?
> Which version is that?
>

I no longer  have a working version of sage. 

>
> Have you tried installing the SageMath 8.6 binary for macOS from
>
> http://www.sagemath.org/download-mac.html
>
> I need the source distribution as  I am developing code (or at least I 
was...)

>
> Have you re-installed XCode after installing macOS 10.14 Mojave?
>
yes 

>
> What is the output of
> ```
> xcode-select --version
>
As noted above I am running:
ProductName:Mac OS X
ProductVersion:10.14.2
BuildVersion:18C54
Xcode 10.1
Build version 10B61
and have already installed xcode andthe system headers,


You could remove the pip tarball in case it is corrupted:
> ``` 
> rm /usr/local/src/sage/upstream/pip-18.1.tar.gz
> rm -rf /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
> ```
> You could move the old build logs out of the way
> ```
> mv /usr/local/src/sage/logs /usr/local/src/sage/logs-old
>

Good idea. Will try this.

> ```
>
> You could try to make distclean, configure and make:
> ```
> cd /usr/local/src/sage
> make distclean
> make configure
> ./configure
> make
>

Out of curiosity, doesn't make run configure automatically?  

I have tried make distclean && make a few times already but now that you 
mention it I think that last time I had this p=trouble I deleted the build 
directory and the next compile worked. It will take a while to recompile. 
I"ll let you know how it goes tomorrow.

Andrew
At this pin 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

> The full log is below.
>

Found local metadata for pip-18.1
Using cached file /usr/local/src/sage/upstream/pip-18.1.tar.gz
pip-18.1

Setting up build directory for pip-18.1
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
No patch files found in ../patches

Host system:
Darwin p718m.pc.maths.usyd.edu.au 18.2.0 Darwin Kernel Version 18.2.0: Thu 
Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~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=/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Package 'pip' is currently not installed
No legacy uninstaller found for 'pip'; nothing to do
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.083user 0.042sys 0.027pcpu 84.11


Error installing package pip-18.1

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.1.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1 and type 'make' or 
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1' && 
'/usr/local/src/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.

Found local metadata for pip-18.1
Using cached file /usr/local/src/sage/upstream/pip-18.1.tar.gz
pip-18.1

Setting up build directory for pip-18.1
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
No patch files found in ../patches

Host system:
Darwin p718m.pc.maths.usyd.edu.au 18.2.0 Darwin Kernel Version 18.2.0: Thu 
Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~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=/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Package 'pip' is currently not installed
No legacy uninstaller found for 'pip'; nothing to do
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.098user 0.044sys 0.027pcpu 72.94


Error installing package pip-18.1

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.1.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1 and type 'make' or 
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1' && 
'/usr/local/src/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.

Found local metadata for pip-18.1
Using cached file /usr/local/src/sage/upstream/pip-18.1.tar.gz
pip-18.1
=

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

I'm not seeing a ModuleNotFoundError error.  Above, when i mentioned using 
sage -sh, I tried this only after your suggestion of

./sage -f zlib python2 python3
make

failed. Running

make distclean && make 

still gives me the pip-18.1 error and adding

./sage -f zlib python2 python3 && make

gives me the pip-18.1 i error again. The relevant part of the install log 
seems to be:

Package 'pip' is currently not installed
No legacy uninstaller found for 'pip'; nothing to do
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
/usr/local/src/sage/local/bin/python3: No module named pip

The full log is below.
Andrew


On Tuesday, 19 February 2019 10:37:41 UTC+11, John H Palmieri wrote:
>
> On one of my machines running OS X Mojave, when I run 'make', the pip 
> installation fails, saying 
>
> ModuleNotFoundError: No module named 'zlib'
>
> That's when the solution is
>
> ./sage -f zlib python2 python3
> make
>
> --- pip-18.1 install log 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

On Tuesday, 19 February 2019 03:44:02 UTC+11, John H Palmieri wrote:
>
> Can you post the end of the file logs/pkgs/pip-18.1.log? The last 30 lines 
> or so? Or post the whole file if you can.
>
> The log from after the failed make is s below. It says that 
No record that 'pip' was ever installed; skipping uninstall
I've tried going into the sage sh and using easy_install 2-7 and 3.6 to 
install pip (as in 
https://groups.google.com/forum/#!topic/sage-release/XUYlh2DHP9E) and then 
running make but, again, I end up with pip-18.1 not installed. The problem 
seems to be that I have pip-19.0.2:

local/bin/pip --version
pip 19.0.2 from 
/usr/local/src/sage/local/lib/python2.7/site-packages/pip-19.0.2-py2.7.egg/pip 
(python 2.7)

install log for pip

Found local metadata for pip-18.1
Using cached file /usr/local/src/sage/upstream/pip-18.1.tar.gz
pip-18.1

Setting up build directory for pip-18.1
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
No patch files found in ../patches

Host system:
Darwin MacAndrew.local 18.2.0 Darwin Kernel Version 18.2.0: Mon Nov 12 
20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64 x86_64

C compiler: gcc
C compiler version:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

No record that 'pip' was ever installed; skipping uninstall
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.096user 0.054sys 0.033pcpu 90.38


Error installing package pip-18.1

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.1.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1 and type 'make' or 
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1' && 
'/usr/local/src/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.

Found local metadata for pip-18.1
Using cached file /usr/local/src/sage/upstream/pip-18.1.tar.gz
pip-18.1

Setting up build directory for pip-18.1
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
No patch files found in ../patches

Host system:
Darwin MacAndrew.local 18.2.0 Darwin Kernel Version 18.2.0: Mon Nov 12 
20:24:46 PST 2018; root:xnu-4903.231.4~2/RELEASE_X86_64 x86_64

C compiler: gcc
C compiler version:
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 10.0.0 (clang-1000.11.45.5)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

No record that 'pip' was ever installed; skipping uninstall
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.1/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.097user 0.053sys 0.036pcpu 91.13


Error installing package pip-18.1

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.1.log
Describe your computer, operating system, etc.
If you wa

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

Thanks John. Unfortunately, zlib and python 2 and 3 compile then then make 
fails again on pip-18.1.
I tried a couple of different variations on this but it always ended up at 
the same place.

What else should I look for? Is make distclean the best way to get back to 
a clean install? It's not unlikely that I have something borked things up.

Andrew

On Monday, 18 February 2019 17:46:24 UTC+11, John H Palmieri wrote:
>
> Please try:
>
> ./sage -f zlib
> ./sage -f python2
> ./sage -f python3
>
> and if those work, try 'make' again.
>
>   John
>
>
>
> On Sunday, February 17, 2019 at 6:11:51 PM UTC-8, Andrew wrote:
>>
>> I have been unable to compile sage for a while on both an imac and a 
>> macbook pro that are running mojave (clearly my mistake for installing 
>> it...). I have installed the system headers, so that's unlikely to be the 
>> problem. 
>>
>> Everytime that I try to compile I get stuck on:
>>
>> The following package(s) may have failed to build (not necessarily
>> during this run of 'make all-start'):
>>
>> * package: pip-18.1
>>   log file: /usr/local/src/sage/logs/pkgs/pip-18.1.log
>>   build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1
>>
>> The build directory may contain configuration files and other potentially
>> helpful information. WARNING: if you now run 'make' again, the build
>> directory will, by default, be deleted. Set the environment variable
>> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>>
>> I am running: 
>>
>> ProductName:Mac OS X
>> ProductVersion:10.14.3
>> BuildVersion:18D109
>> Xcode 10.1
>> Build version 10B61
>>
>> The logs after: makedistcean && make are too big to attach but if 
>> interested you can find them at 
>> http://www.maths.usyd.edu.au/u/mathas/install.log.
>>
>> Any hints would be greatly appreciated.
>>
>> Andrew
>>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Unable to compile sage 8.7.beta3 on mojave...

[Andrew]

I have been unable to compile sage for a while on both an imac and a 
macbook pro that are running mojave (clearly my mistake for installing 
it...). I have installed the system headers, so that's unlikely to be the 
problem. 

Everytime that I try to compile I get stuck on:

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: pip-18.1
  log file: /usr/local/src/sage/logs/pkgs/pip-18.1.log
  build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.1

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

I am running: 

ProductName:Mac OS X
ProductVersion:10.14.3
BuildVersion:18D109
Xcode 10.1
Build version 10B61

The logs after: makedistcean && make are too big to attach but if 
interested you can find them at 
http://www.maths.usyd.edu.au/u/mathas/install.log.

Any hints would be greatly appreciated.

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Can't compile 8.4.beta3

[Andrew]

It turns out that this is issue with 8.4.beta1 that Steven highlighted 
above, although the fix that I needed has a few more steps. I'll post 
details in sage-release under 8.4.beta1. In any case, I now have a working 
version of  8.4.beta4.

Thanks Steven, John and Erik for your help!
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Can't compile 8.4.beta3

[Andrew]

Dear John and Erik,

Thanks for the hints. I have tried recompiling several times as suggested 
but the build still fails, sometimes on pip-18.0 and sometimes on 
python3-3.6.6.p0. Given the potential race condition in 
https://trac.sagemath.org/ticket/18438 I'll try compiling with a single 
core and see if this works.

Andrew

On Tuesday, 11 September 2018 01:22:55 UTC+10, Erik Bray wrote:
>
> On Mon, Sep 10, 2018 at 6:33 AM John H Palmieri  > wrote: 
> > 
> > One thing to try, in case you haven't already: run make once, and if it 
> fails with a warning like this, try running make again immediately (without 
> doing "make distclean"). (Sage may be using Sage's python in the 
> installation process before it's quite ready, but when you run 'make' a 
> second time, the installation of python2 will have completed.) 
>
> +1 You're probably running into https://trac.sagemath.org/ticket/18438 
>  which is a race condition in parallel builds. 
>
> Just re-run `make` without doing `make distclean` and it should continue. 
>
> > On Sunday, September 9, 2018 at 9:28:11 PM UTC-7, Andrew wrote: 
> >> 
> >> I'm now trying, without success, to compile 8.4.beta4. 
> >> 
> >> I have homebrew installed. For the past few years I have stopped it 
> from affecting the sage compliation by setting my PATH accordingly. If I do 
> this and use 
> >> make distclean && make 
> >> 
> >> then I still the error above with make failing on pip-18.0. Here is the 
> pip-18.0.log file: 
> >> 
> >> pip-18.0 
> >>  
> >> Setting up build directory for pip-18.0 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 
> >> Finished extraction 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src 
> >> No patch files found in ../patches 
> >>  
> >> Host system: 
> >> Darwin p718m.pc.maths.usyd.edu.au 17.7.0 Darwin Kernel Version 17.7.0: 
> Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~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=/usr/include/c++/4.2.1 
> >> Apple LLVM version 9.1.0 (clang-902.0.39.2) 
> >> Target: x86_64-apple-darwin17.7.0 
> >> Thread model: posix 
> >> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>  
>
> >>  
> >> No record that 'pip' was ever installed; skipping uninstall 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src 
> >> /usr/local/src/sage/local/bin/python3: No module named pip 
> >> 
> 
>  
>
> >> Error building / installing pip3 
> >> 
> 
>  
>
> >> 
> >> real 0.102  user 0.044  sys 0.024   pcpu 67.51 
> >> 
> >> 
>  
> >> Error installing package pip-18.0 
> >> 
>  
> >> Please email sage-devel (http://groups.google.com/group/sage-devel) 
> >> explaining the problem and including the log file 
> >>   /usr/local/src/sage/logs/pkgs/pip-18.0.log 
> >> Describe your computer, operating system, etc. 
> >> If you want to try to fix the problem yourself, *don't* just cd to 
> >> /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 and type 'make' 
> or whatever is appropriate. 
> >> Instead, the following commands setup all environment variables 
> >> correctly and load a subshell for you to debug the error: 
> >>   (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0' && 
> '/usr/local/src/sage/sage' --sh) 
> >> When you are done debugging, you can type "exit" to leave the subshell. 
> >> 
>  
> >> 
> >> make distclean && make I hit an error compiling python3-3.6.6.p0. The 
> log file python3.6 is attached. 
> >> 
> >> If, instead, I run make distclean && make without 

[sage-devel] Re: Can't compile 8.4.beta3

[Andrew]

I'm now trying, without success, to compile 8.4.beta4. 

I have homebrew installed. For the past few years I have stopped it from 
affecting the sage compliation by setting my PATH accordingly. If I do this 
and use 
make distclean && make 

then I still the error above with make failing on pip-18.0. Here is the 
pip-18.0.log file:

pip-18.0

Setting up build directory for pip-18.0
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
No patch files found in ../patches

Host system:
Darwin p718m.pc.maths.usyd.edu.au 17.7.0 Darwin Kernel Version 17.7.0: Thu 
Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~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=/usr/include/c++/4.2.1
Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/
XcodeDefault.xctoolchain/usr/bin

No record that 'pip' was ever installed; skipping uninstall
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.102  user 0.044  sys 0.024   pcpu 67.51


Error installing package pip-18.0

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.0.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 and type 'make' or 
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0' && '/usr/local
/src/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.


make distclean && make I hit an error compiling python3-3.6.6.p0. The log 
file python3.6 is attached.

If, instead, I run make distclean && make without removing brew then I get 
a little further, with make now breaking on the build of python3-3.6.6.p0, 
with 
python3-3.6.6.p0.log now looking like:


Found local metadata for python3-3.6.6.p0
Traceback (most recent call last):
  File "/usr/local/src/sage/local/lib/python2.7/site.py", line 62, in 

import os
  File "/usr/local/src/sage/local/lib/python2.7/os.py", line 49, in 
import posixpath as path
  File "/usr/local/src/sage/local/lib/python2.7/posixpath.py", line 17, in 

import warnings
ImportError: No module named warnings

Error downloading Python-3.6.6.tar.gz

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/python3-3.6.6.p0.log
Describe your computer, operating system, etc.

I am seeing the same behaviour on an imac and on a macbook pro. both of 
which are running:
ProductName:Mac OS X
ProductVersion:    10.13.6
BuildVersion:17G65
Xcode 9.4.1
Build version 9F2000
Does anyone have  an idea of what's going wrong here?

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for python3-3.6.6.p0
Traceback (most recent call last):
  File "/usr/local/src/sage/local/lib/python2.7/site.py", line 62, in 
import os
  File "/usr/local/src/sage/local/lib/python2.7/os.py", line 49, in 
import posixpath as path
  File "/usr/local/src/sage/local/lib/python2.7/posixpath.py", line 17, in 

 

Re: [sage-devel] Can't compile 8.4.beta3

[Andrew]

On Thursday, 6 September 2018 22:40:37 UTC+10, Jeroen Demeyer wrote:
>
> On 2018-09-06 08:21, Andrew wrote: 
> > *package:pip-18.0 
> >log file:/usr/local/src/sage/logs/pkgs/pip-18.0.log 
>
> attach this log file please ^ 
>
> Here's the log (Australia sleeps when the rest of the world doesn't hence 
the delay:)

Found local metadata for pip-18.0
Using cached file /usr/local/src/sage/upstream/pip-18.0.tar.gz
pip-18.0

Setting up build directory for pip-18.0
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
No patch files found in ../patches

Host system:
Darwin p718m.pc.maths.usyd.edu.au 17.7.0 Darwin Kernel Version 17.7.0: Thu 
Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~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=/usr/include/c++/4.2.1
Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

No record that 'pip' was ever installed; skipping uninstall
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.092user 0.042sys 0.025pcpu 73.17


Error installing package pip-18.0

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.0.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 and type 'make' or 
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0' && 
'/usr/local/src/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.

Found local metadata for pip-18.0
Using cached file /usr/local/src/sage/upstream/pip-18.0.tar.gz
pip-18.0

Setting up build directory for pip-18.0
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0
Finished extraction
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
No patch files found in ../patches

Host system:
Darwin p718m.pc.maths.usyd.edu.au 17.7.0 Darwin Kernel Version 17.7.0: Thu 
Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~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=/usr/include/c++/4.2.1
Apple LLVM version 9.1.0 (clang-902.0.39.2)
Target: x86_64-apple-darwin17.7.0
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

No record that 'pip' was ever installed; skipping uninstall
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0/src
/usr/local/src/sage/local/bin/python3: No module named pip

Error building / installing pip3


real 0.109user 0.045sys 0.025pcpu 63.94


Error installing package pip-18.0

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /usr/local/src/sage/logs/pkgs/pip-18.0.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/src/sage/local/var/tmp/sage/build/pip-18.0 and type 'make' or 
whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/usr/l

[sage-devel] Can't compile 8.4.beta3

[Andrew]

I'm not able compile any of the 8.4 betas on both my laptop and a desktop 
machine. I had no problem with 8.3 betas. 

Quite possibly I am doing, or have done, something stupid but I don't think 
that I have changed anything from 8.3. I am running

ProductName:Mac OS X
ProductVersion:10.13.6
BuildVersion:17G65
Xcode 9.4.1
Build version 9F2000

The full log file is too large to attach so I have put in on install.log 
<http://www.maths.usyd.edu.au/u/mathas/install.log>, but the last message is

***
Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: pip-18.0
  log file: /usr/local/src/sage/logs/pkgs/pip-18.0.log
  build directory: /usr/local/src/sage/local/var/tmp/sage/build/pip-18.0

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

Can anyone see what I am doing wrong?

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Names of objects in sage

[Andrew]

maybe what you need is to write a _sage_input_ method for those objects, 
>

For multivariate polynomials see https://trac.sagemath.org/ticket/25723. I 
haven't posted for review yet as there seem to be some seemingly unrelated 
failing doc-tests. Will look into these when I have some  time tonight.
 

> I agree that it would be amazing to have every _repr_ be copy-pastable, 
>

Gap does, or at least did, aim to do this. 
 

> but then how do you want to render simple things like QQbar(1) without 
> being heavy ? 
>
 
QQbar is less heavy than the the current "Algebraic Field".

>
> By the way, there is already: 
>
> sage: sage_input(PolynomialRing(GF(5), 'q')) 
> GF(5)['q'] 
>

Thank you! I did not know about sage_input or that this input for 
polynomial rings was accepted. The point of my post is that in many cases 
the output of sage_input would be a better _repr_.

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Names of objects in sage

[Andrew]

For some reason in sage when printing we often use long and laborious names 
like:

sage: LaurentPolynomialRing(ZZ,'q')
Univariate Laurent Polynomial Ring in q over Integer Ring
sage: LaurentPolynomialRing(GF(5),'q')
Univariate Laurent Polynomial Ring in q over Finite Field of size 5

Is there any reason why we print things like this? One alternative is to 
try and approximate more readable standard notation, such as:

ZZ[q]
F5[q]

Alternatively, we could use something that can be used to reproduce the 
object, by cutting and pasting, such as

PolynomialRing(GF(5),'q')

In fact, by overloading __getitem__ we could even use

GF(5)['q']

to both *create* polynomial rings and to *print* them. 

The current implementations of _repr_ gets somewhat ridiculous when we 
combine these naming conventions in classes like CombinatorialFreeModules 
where we end up producing things like:

sage: IwahoriHeckeAlgebra('A3',q,1)
Iwahori-Hecke algebra of type A3 in q,1 over Univariate Polynomial Ring in 
q over Finite Field of size 5


If you happen to be working over nested multivariate  polynomial rings, as 
I happen to be at the moment, then it can take 3-4 lines to print the 
object. Personally, in the last case I would rather print

IwahoriHeckeAlgebra('A3',q,1)

because it is both more readable and it allows me to reproduce the object. 

Is it just me or do others think that there is a problem here? Of course, 
ultimately, 
the underlying algorithms and code is much more important but, still, 
appearances do mater and the whole point of _repr_ is to give an easily 
understandable description of the underlying object. I am not sure that 
opting fo verbose non-standard names really achieves this.

If there's support I am happy to open a ticket and work on this, even 
though it will almost certainly be huge a patch bomb.

OK, end of rant,
Andrew

 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Potential bug multiplying permutations from subgroups

[Andrew]

Is this me or is it a bug?

sage: S3 = SymmetricGroup(3)
sage: A3 = S3.subgroup([(1,2,3)])
: for x in S3:
: print('{:>7}: left coset  = {}'.format(x, [x*h for h in A3]))
: print('   : right coset = {}'.format([h*x for h in A3]))
:

 (): left coset  = [(), (1,2,3), (1,3,2)]
   : right coset = [(), (1,2,3), (1,3,2)]
  (1,2): left coset  = [(1,2), (1,3), (2,3)]
---
TypeError Traceback (most recent call last)
...
TypeError: unsupported operand parent(s) for *: 'Subgroup of (Symmetric 
group of order 3! as a permutation group) generated by [(1,2,3)]' and 
'Symmetric 
group of order 3! as a permutation group'
> /Users/andrew/Downloads/sage/structure/coerce.pyx(1168)sage.structure.
coerce.CoercionModel_cache_maps.bin_op (build/cythonized/sage/structure/
coerce.c:10861)()

I threw this into a sage notebook with the view to showing my students the 
virtues of normal subgroups...

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: OS X (or BSD) testers needed

[Andrew]

Using 

ProductName:Mac OS X
ProductVersion:10.13.3
BuildVersion:17D47
Xcode 9.2
Build version 9C40b



and gcc --version

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --
with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 9.0.0 (clang-900.0.39.2)
Target: x86_64-apple-darwin17.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/
XcodeDefault.xctoolchain/usr/bin

I get the output:

Darwin pmathas3.pc.maths.usyd.edu.au 17.4.0 Darwin Kernel Version 17.4.0: 
Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64 x86_64

> If you have an OS X (or BSD) system installed with development tools, 
> please run: 
>
> uname -a 
> gcc forksigaltstack.c -o forksigaltstack && ./forksigaltstack 
>
> and post the output. This code is a reduction of a test failure in 
> cysignals. I consider that failure to be an OS X bug. I want to have 
> some better idea of which systems are affected. 
>
> The expected output is 
>
> got signal 11 
> status = 0 
>
> but on some (presumably broken) systems I get 
>
> status = 4 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Whitespace patchbombs

[R. Andrew Ohana]

If I recall, when I originally setup the git-trac server, I included a hook
that would reject/warn any introduction of new trailing whitespace. I
believe this was a compromise made after a long discussion at a Sage days
-- there were a lot of concerns at the time about the effort required to
rebase mercurial patches with conflicts arising from a whitespace
patchbomb. I also believe that we included in the documentation and server
side hook a suggestion to use the trailing whitespace stripping commit hook
(and there was a sage-dev command that would automatically do that,
although sage-dev has now been removed in favor of vanilla git or Volker's
git trac).

On Tue, Feb 20, 2018 at 12:47 PM, Jeroen Demeyer  wrote:

> Interesting fact: the number of lines with trailing whitespace is
> generally *increasing* with every Sage release. So it seems to me that the
> biggest problem (if you find whitespace a problem) is preventing new
> whitespace.
>
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: making database_gap (starting from GAP 4.9) standard - please vote

[Andrew]

+1
Andrew

On Monday, 19 February 2018 02:18:10 UTC+11, Eric Gourgoulhon wrote:
>
> Le dimanche 18 février 2018 00:01:50 UTC+1, Dima Pasechnik a écrit :
>>
>>
>> Thus I'm calling for a vote on this: to make database_gap standard as 
>> soon as license permits (i.e. as soon as we update to GAP 4.9).
>>
>
> +1
>
> 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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] installation of sage 8.0 failed on on mac os 10.13.1

[Andrew]

#24085 is merged in Sage 8.1.rc4. I am compiling 8.1.rc4 now on a macbook 
pro with a skylake cpu and the mpir issue appears to be fixed (mpir 
finished compiling a while ago and the compile has almost finished). Of 
course, I still need to run the tests. 
<https://groups.google.com/forum/#!topic/sage-release/6OINE_odkEc>

I m using maxosx 10.12.6, so it is possible that there could be issues, 
with mpir or elsewhere,  with 
<https://groups.google.com/forum/#!topic/sage-release/6OINE_odkEc>10.13.1. 
I have not upgraded to 10.13.1 yet precisely because apple has a hait of 
screwing up xcode with every new release and I don't want to risk it.

Andrew


On Thursday, 30 November 2017 19:28:42 UTC+1, David Roe wrote:
>
> This is very likely the issue being tracked at #24085 
> <https://trac.sagemath.org/ticket/24085>, and is a result of building 
> Sage on a Mac with a Skylake processor.  There's currently a debate going 
> there about how to package a solution in a way to make it into sage-8.1.  
> If anyone has opinions, feel free to chime in.
> David
>
> On Thu, Nov 30, 2017 at 11:40 AM, > 
> wrote:
>
>>
>> I tried to install sage 8.0 on a mac book pro with mac os 10.13.1
>> The following error occurred
>>
>> Error installing package mpir-3.0.0.p0
>>
>> Could you help me solving this problem?
>>
>> I attached the log file.
>>
>> Thanks!
>>
>> Best
>> Simon
>>
>> -- 
>> 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 post to this group, send email to sage-...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Issue with quick start

[Andrew]

On Wednesday, 29 November 2017 10:18:54 UTC+1, John Cremona wrote:
>
> Please can we just use "mathematics" and not argue about abbreviations? 
>
> +1

As an Australian,"math" sounds as wrong to me as I imagine that "maths" 
does to north Americans.

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Proposal : a branch for OpenSSL-less Sage

[Andrew]

On Friday, 27 October 2017 17:03:00 UTC+2, Emmanuel Charpentier wrote:

> Heck, go ahead even and drop that patch if you want, just as long as 
>> there are clear instructions for OSX users how to build. 
>>
>
> Indeed : I'm relying on people with knowledge of Mac OS X and its 
> shenanigans (a. k. a. "our Mac heads") for that.
>

What's the status of using sage with homebrew these days (I use it but have 
a
bash function to compile sage in a "brew free" environment). If sage does 
play
well with homebrew then installing sage on a mac is trivial:

1. Install homebrew
2. brew install opensll
 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Unable to compile 8.0.rc2 on mac

[Andrew]

On Wednesday, 19 July 2017 00:59:27 UTC+10, Dima Pasechnik wrote:
>
> Surely MPIR guys would appreciate feedback.
> This might be their assembler bug.
>
> Will let them know.
A. 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Unable to compile 8.0.rc2 on mac

[Andrew]

You're probably right as I have managed to rebuild 8.0.beta4 from scratch. 
I won't attempt to build for a while:)

Thanks.
Andrew

On Tuesday, 18 July 2017 17:36:30 UTC+10, François Bissey wrote:
>
> No 8.0.beta4 had an older version of mpir. 
>
> François 
>
> > On 18/07/2017, at 18:47, Andrew > 
> wrote: 
> > 
> > I managed to compile 8.0.beta4 without issues but perhaps xcode has 
> changed in the interim... 
> > 
> > Andrew 
> > 
> > On Tuesday, 18 July 2017 14:54:56 UTC+10, François Bissey wrote: 
> > You appear to have some relatively recent hardware. I am suspecting 
> > that the combination OS X + skylake cpu hasn’t had a lot of testing. 
> > Not sure how to get around that really. 
> > 
> > François 
> > 
> > > On 18/07/2017, at 16:32, Andrew  wrote: 
> > > 
> > > I'm trying to compile the current sagemath dev version 8.0.rc2 but am 
> continually getting an error with mpir-3.0.0.p0. I've tried 
> > > 
> > > git clean -f -d -x && make clean && make build 
> > > 
> > > but cannot get it to compile. I have a macbook pro that is using 
> macosx 10.12.5 with xcode 8.3.3 (build 8E3004b) and xcode-select version 
> 2347. The latest build log is attached. 
> > > 
> > > Any ideas how to get around this? 
> > > 
> > > Andrew 
> > > 
> > > 
> > > -- 
> > > 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 post to this group, send email to sage-...@googlegroups.com. 
> > > Visit this group at https://groups.google.com/group/sage-devel. 
> > > For more options, visit https://groups.google.com/d/optout. 
> > >  
> > 
> > 
> > -- 
> > 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 post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Unable to compile 8.0.rc2 on mac

[Andrew]

I managed to compile 8.0.beta4 without issues but perhaps xcode has changed 
in the interim...

Andrew

On Tuesday, 18 July 2017 14:54:56 UTC+10, François Bissey wrote:
>
> You appear to have some relatively recent hardware. I am suspecting 
> that the combination OS X + skylake cpu hasn’t had a lot of testing. 
> Not sure how to get around that really. 
>
> François 
>
> > On 18/07/2017, at 16:32, Andrew > 
> wrote: 
> > 
> > I'm trying to compile the current sagemath dev version 8.0.rc2 but am 
> continually getting an error with mpir-3.0.0.p0. I've tried 
> > 
> > git clean -f -d -x && make clean && make build 
> > 
> > but cannot get it to compile. I have a macbook pro that is using macosx 
> 10.12.5 with xcode 8.3.3 (build 8E3004b) and xcode-select version 2347. The 
> latest build log is attached. 
> > 
> > Any ideas how to get around this? 
> > 
> > Andrew 
> > 
> > 
> > -- 
> > 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 post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
> >  
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: sage-8.0 beta and python3

[Andrew]

Is there a significant change behind going from version 7.6 to 8.0?
Andrew

On Saturday, 8 April 2017 03:14:01 UTC+10, vdelecroix wrote:
>
> On 07/04/2017 19:03, John H Palmieri wrote: 
> > Python 3 is also built and installed by default in Sage, at least in 
> recent 
> > development versions, for use by developers trying to make Sage 
> compatible 
> > with Python 3. 
>
> Indeed, you can use it 
>
> $ sage -sh -c "python3" 
> Python 3.5.1 (default, Apr  7 2017, 09:24:58) 
> [GCC 6.3.1 20170109] on linux 
> Type "help", "copyright", "credits" or "license" for more information. 
>  >>> 
>
> BTW, I wonder why Python3 is not visible in the jupyter notebook... 
> would be nice to have it available in the list of kernels. 
>
> Vincent 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: BGG Sage microbadge

[Andrew]

Ah, so not Bernstein-Gelfand-Gelfand then...


On Sunday, 19 February 2017 13:59:14 UTC+11, kcrisman wrote:
>
> For those who are true board game geeks (of which I know a number on this 
> list):
>
> https://boardgamegeek.com/microbadge/9453
>
> I have no idea who the creator is, but hats off!
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] cysignals version still 1.1.1?

[Andrew]

Probably related to 
https://groups.google.com/forum/#!topic/sage-support/jKbvdQbIPAo

On Wednesday, 9 November 2016 21:54:02 UTC+11, Jeroen Demeyer wrote:
>
> On 2016-11-09 10:32, Dima Pasechnik wrote: 
> > I notice that 1.1.1 is the latest "shipped" by Sage (and in the latest 
> > develop branch), while https://github.com/sagemath/cysignals is at 
> 1.3.2. 
> > Just wondering if this is right, and no disconnect has happened. 
>
> https://trac.sagemath.org/ticket/21653 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: ReST References in Sphinx and uniqueness

[Andrew]

In any large document, such as the sage manuals, there are bound to be 
uniqueness issues with the choice of labels for references. The best way to 
resolve this is for us to start using a specified format for the 
references. Currently we do not even have guidelines for this so it is not 
surprising that different people do different things.

It would also help to have the references appearing in one file, as William 
suggests, so that people can find them easily and check that the label does 
not already exist. A reference file would also help ensure that people use 
whatever format is agreed upon for the references.

Andrew

On Tuesday, 6 September 2016 07:49:42 UTC+10, John H Palmieri wrote:
>
>
>
> On Monday, September 5, 2016 at 11:20:15 AM UTC-7, Johan S. R. Nielsen 
> wrote:
>>
>> leif writes: 
>> >> ... [HP] W. C. Huffman, V. Pless, Fundamentals of Error-Correcting 
>> >>Codes, Cambridge Univ. Press, 2003. 
>> > 
>> > Well, first of all it is stupid to use such a short abbreviation, even 
>> > without a year.  Presumably it was introduced when references were 
>> > local, so we may create a (meta-)ticket to change all of such 
>> occurrences. 
>>
>> Agreed. The inspiration for new developers in the Sage Development 
>> manual uses the citation label "[SC]": 
>>
>>
>> http://doc.sagemath.org/html/en/developer/coding_basics.html#documentation-strings
>>  
>>
>>
>> >> Is this sort of mess the reason Sphinx is so terribly slow, I 
>> wonder... 
>> > 
>> > Well, not that long ago, docbuilding in parallel wasn't even possible 
>> > (h/t mostly John Palmieri IIRC, with a few others); before, the whole 
>> > reference manual had been one monolithic block. 
>> > 
>> > Of course the documentation keeps growing (and hence also Sphinx' 
>> memory 
>> > footprint and runtime), but it was IMHO always double dog-slow.  But 
>> > especially building plot* gets slower and slower because people keep 
>> > adding more and more "nice" things I guess. 
>> > 
>> > To me the most annoying thing is that "make doc" (which ptestlong for 
>> > example for no reason depends on) meanwhile even takes ages when Sphinx 
>> > does nothing, or almost nothing, because nothing changed.  (My recent 
>> > impression is though that some files accidentally get touched somehow, 
>> > such that they to Sphinx look modified.  I can't give any concrete 
>> > example, just noticed.) 
>>
>> Yes, doing `make doc` goes through every chapter of the manual, very 
>> carefully determining that nothing changed. I often use "./sage 
>> -docbuild reference/ html" instead, but that seems even more 
>> fragile than regular doc-building. 
>>
>> Jeroen Demeyer writes: 
>> > General comment to all people complaining about Sphinx: reviewing 
>> > existing Sphinx-related tickets such as #20577 will show that you 
>> > actually care and will encourage other Sage developers to continue 
>> > working on Sphinx. 
>>
>> Thanks for your work! Are there tickets (or upstream-not-merged-changes) 
>> which would make Sphinx faster or have better, less fragile incremental 
>> building? 
>>
>> Best, 
>> Johan 
>>
>
> Regarding speed, there are two issues:
>
> 1. Building the documentation from scratch. I don't  know if we can expect 
> this to go any faster. The PDF version of the documentation is 3,474 pages 
> long. No, wait, that's just the contribution from references/combinat: the 
> whole reference manual is 18,442 pages long. I can build this on my machine 
> in about 8 minutes, and this does not seem unreasonable. Am I wrong about 
> this? (It could be sped up a bit for parallel builds if the largest pieces, 
> e.g., reference/combinat, were broken into smaller pieces, but I don't know 
> how much speed increase we can hope for.)
>
> 2. Incremental builds. I agree that this is not very fast, and it doesn't 
> play well when switching between git branches: too much of the 
> documentation is rebuilt, and the docbuild often fails (e.g., if Python 
> source files have been removed from one branch to another). I don't know 
> how to fix these issues.
>
> By the way, the main work for allowing parallel docbuilding was done by 
> Mitesh Patel, not me (although I helped a little).
>
> -- 
> John
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: (William Stein) "my top priority right now is to **make a lot of money**"

[Andrew]

Nathan does give the link to the original post, but he is quoting out of 
context. Here is the full post:

On Sunday, 21 August 2016 07:15:56 UTC+10, William wrote:

> So there is no confusion, my top priority right now is to **make a lot 
> of money** by building a profitable company on open source software 
> (Latex, Linux, Sage, Octave, R, etc.), and use that money to fund: 
>
>1. Sage development, 
>
>2. Vastly improve the *documentation* ecosystem around Sage, 
>
>3. Vastly improve the *support* ecosystem around Sage, especially 
> for the masses beyond elite research mathematicians. 
>
> You may strongly disagree with this, or chose not to be involved in 
> Sage (or LInux, say) as a result.  But to be clear -- I'm not hiding 
> this. 
>
>  -- William 
>


On Thursday, 25 August 2016 06:12:56 UTC+10, Nathann Cohen wrote:
>
> Quote from William Stein, CEO of SageMath Inc (private for-profit 
> Delaware company) [1] 
>
> So there is no confusion, my top priority right now is to **make a lot 
> of money** by building a profitable company on open source software 
> (Latex, Linux, Sage, Octave, R, etc.) 
>
> (full post) 
> https://groups.google.com/d/msg/sage-devel/B3WnJr6S1bw/JQ_jvOITBAAJ 
>
> This post being entirely factual, I shouldn't be held responsible for 
> its content. 
>
> Nathann 
>
> [1] 
> http://www.edgarcompany.sec.gov/servlet/CompanyDBSearch?page=detailed&cik=0001634867&main_back=23
>  
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Parent structure class hierarchy

[Andrew]

On Friday, 5 August 2016 18:23:03 UTC+10, Simon King wrote:

> So, my advice is: 
> - Start with one of the element base classes and implement arithmetics 
>   there (and be careful to comply with Sage's coercion model). 
> - Use the category framework to determine whether a parent it is a (say) 
>   ring or a module. 
> - CombinatorialFreeModule is convenient, but any time critical stuff 
>   should be implemented on the level of its elements. 
>

Hi Simon,

Would you mind expanding a little on this? I have some modules, for the 
symmetric groups for example, that are implemented using  
CombinatorialFreeModule, together with the realization code as there are 
several interesting bases. It's reasonably fast in "small" examples but I'd 
be happy if there was a way to make it faster. The indexing set for the 
basis has a lot of combinatorial data attached to it that described 
important properties of the module -- for example, it is graded and the 
indexing set gives the grading -- so I need the indexing set. The algebra 
action is defined by certain linear maps on the basis elements.. In 
different incarnations these modules are defined over Z, or any ring, or 
QQ[x]. How would you recommend implementing this?

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installing optional packages

[Andrew]

On Wednesday, 27 July 2016 18:13:44 UTC+10, leif wrote:
>
> Andrew wrote: 
> > I just installed an optional package but it took me a while to remember 
> > how to do it. Of course, it is completely straightforward but I just 
> > forgot 
>
> Ahem, './sage --help'? 
>
> Sure that's what I did when I didn't find it i the manual. The point is 
that it should ALSO be in the manual.
 

> That points you to './sage --advanced' (advanced help) as well, which 
> gives 
>
> Installing packages and upgrading: 
>   -package [args] -- call the new package manager with given 
> arguments. 
>  Run without arguments for package-specific help. 
>   -experimental   -- list all experimental packages that can be 
> installed 
>   -f [opts] [packages]-- shortcut for -i -f: force build of the given Sage 
>  packages 
>   -i [opts] [packages]-- install the given Sage packages.  Options: 
>-c -- run the packages' test suites 
>-d -- only download, do not install packages 
>-f -- force build: install the packages even 
>  if they are already installed 
>-s -- do not delete the temporary build 
> directories 
>  after a successful build 
>   -p [opts] [packages]-- install the given Sage packages, without 
> dependency 
>  checking and with support for old-style spkgs. 
>  Options are -c, -d and -s with the same meaning 
> as 
>  for the -i command 
>   -info [packages]-- print the SPKG.txt of the given packages 
>   --location  -- if needed, fix paths to make Sage relocatable 
>   -optional   -- list all optional packages that can be installed 
>   -standard   -- list all standard packages that can be installed 
>   -installed  -- list all installed packages 
>   -upgrade [version]  -- download, build and install the given version. 
> Here, 
>  'version' is a git branch or tag name. Useful 
> values 
>  are 'master' (the current development version, 
> this 
>  is the default) or a version number like '5.13'. 
>   -pip [...]  -- invoke pip, the Python package manager 
>
>
> besides further usage help on other topics. 
>
>
> -leif 
>
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Installing optional packages

[Andrew]

This is now https://trac.sagemath.org/ticket/21101

On Wednesday, 27 July 2016 10:18:59 UTC+10, Andrew wrote:
>
> I just installed an optional package but it took me a while to remember 
> how to do it. Of course, it is completely straightforward but I just 
> forgot
>
> The first place that I looked was in the "Installation guide". There is a 
> section there on "standard packages" but nothing on "optional packages". Is 
> there any objection to adding such a section?
>
> A.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Installing optional packages

[Andrew]

I just installed an optional package but it took me a while to remember how 
to do it. Of course, it is completely straightforward but I just forgot

The first place that I looked was in the "Installation guide". There is a 
section there on "standard packages" but nothing on "optional packages". Is 
there any objection to adding such a section?

A.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Doc-testing ouptut with dots

[Andrew]

Thanks David and Erik for your replies. I could not disable the doct-tests  
so I have changed my output to:

sage: print(CartanType(['A', oo]).ascii_art()) 
..---O---O---O---O---O---O---O---.. 
-3  -2  -1   0   1   2   3


which I think is good enough.

Andrew

On Friday, 8 July 2016 10:34:31 UTC+2, Erik Bray wrote:
>
> On Thu, Jul 7, 2016 at 1:13 PM, Andrew > 
> wrote: 
> > Hi! 
> > 
> > How do you doc-test output that starts with ...? The particular output 
> that 
> > I want to test is: 
> > 
> > sage: print(CartanType(['A', oo]).ascii_art()) 
> > ...---O---O---O---O---O---O---O---... 
> >  -3  -2  -1   0   1   2   3 
> > 
> > but sage complains with: 
> > 
> > 
> > ValueError: line 6 of the docstring for 
> > sage.combinat.root_system.type_A_infinity.CartanType.i lacks blank after 
> > ...: '...---O---O---O---O---O---O---O---...' 
> > 
> > Clearly, sphinx is getting confused because ... normally indicates code 
> > continuation. Is it possible to work around or disable this or do I need 
> to 
> > change my output? 
>
> In the normal doctest framework you can enable and disable such 
> options using the directives documented here: 
> https://docs.python.org/2.7/library/doctest.html#directives  (and it's 
> possible to extend it with additional directives). 
>
> So you should be able to disable ellipsis completion by adding 
>
> # doctest: -ELLIPSIS 
>
> next to your test.  I don't know if for some reason that doesn't work 
> for sage's doctests though.  I see no reason it shouldn't though... 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Doc-testing ouptut with dots

[Andrew]

Hi!

How do you doc-test output that starts with ...? The particular output that 
I want to test is:

sage: print(CartanType(['A', oo]).ascii_art()) 
...---O---O---O---O---O---O---O---... 
 -3  -2  -1   0   1   2   3

but sage complains with:


ValueError: line 6 of the docstring for sage.combinat.root_system.
type_A_infinity.CartanType.i lacks blank after ...: '   
 ...---O---O---O---O---O---O---O---...'

Clearly, sphinx is getting confused because ... normally indicates code 
continuation. Is it possible to work around or disable this or do I need to 
change my output?

Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: {trac,git}.sagemath.org downtime Wednesday 6/22

[Andrew]

When I try to log in to the new trac server I get the error:
Oops…
*Trac detected an internal error:* 

AttributeError: 'FakeSession' object has no attribute 'authenticated'

There was an internal error in Trac. It is recommended that you notify your 
local Trac administrator with the information needed to reproduce the issue.

To that end, you could 

a ticket.

The action that triggered the error was:

POST: /login

TracGuide <https://trac.sagemath.org/wiki/TracGuide> — The Trac User and 
Administration Guide 

I have had this problem since Erik started setting up the new server, and 
no one else seems to have this issue, so it must be something about my set 
up. If any one has any idea what might be wrong please let me know.

Secondly, as trac is now served via a https connection all of the 
references to http://trac.sagemath.org/ in the sage source and 
documentation need to be updated. Has anyone touched this yet? If not then 
I guess I am volunteering (if my connection issue to the trac serverer can 
be resolved, of course!).

Andrew

On Wednesday, 22 June 2016 13:50:15 UTC+2, Erik Bray wrote:
>
> On Wed, Jun 22, 2016 at 1:42 PM, Jeroen Demeyer  > wrote: 
> > Another issue: I no longer get e-mails from Trac. The last e-mail that I 
> > received was on 06:25 CEST (i.e. Paris time). I received nothing more 
> after 
> > that, even though some tickets were changed that I am active on (e.g. 
> > #20852). 
>
> Thanks.  This is probably related: 
> https://cloud.google.com/compute/docs/tutorials/sending-mail/ 
>
> I'll get that patched up. 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Global namespace and independent python packages

[Andrew]

On Thursday, 9 June 2016 17:10:44 UTC+2, Johan S. R. Nielsen wrote:
>
> > from sage.misc.misc import inject_variable 
> > from mytest.test import atest 
> > inject_variable('atest',atest) 
> > 
> > *Question*: do people think that it is reasonable for a package to do 
> this? 
>
> I would also say "No". The reason is that if that is what the user 
> wanted, he could just have done "from mytest import *". If he explicitly 
> does "import mytest" it's because he wants the control over the 
> namespace 

 
Sorry, I didn't fully appreciate your comment above when I first read it. I 
agree, this is fairly compelling.
Andrew 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Global namespace and independent python packages

[Andrew]

Thanks Johan.As much as anything I wanted to know that I wasn't doing 
something stupid.

On Thursday, 9 June 2016 14:02:16 UTC+2, Johan S. R. Nielsen wrote:
>
> As a package author, you shouldn't force the user to load the functions 
> into 
> the global namespace. However, it might be possible by getting hold of the 
> globals() object or something. 
>
 
Well, actually, if some one explicitly loads the package using something 
like "import mytest" then I think that it is reasonable to load the main 
functions from the package it the global namespace. Thinking about it, sage 
already does something similar (but more explicit) with methods like 
inject_shorthands. Drilling down a little I realised that I can do what I 
want by putting the following into my __init__.py file:

from sage.misc.misc import inject_variable
from mytest.test import atest
inject_variable('atest',atest)

*Question*: do people think that it is reasonable for a package to do this?

Arguments against include that packages "shouldn't force the user to load 
the functions into 
the global namespace" and that this may lead to clashes in the namespace. 
An argument in favour of doing this is that this a more user-friendly and a 
user is unlikely to import a package if they don't want to use it.

Andrew


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Global namespace and independent python packages

[Andrew]

I have been playing around with ta stand-alone python package for sage. It 
works really well except that I have not found a "nice" way to import 
classes into the global namespace. I suspect that it is just something in 
the way that I have configured things, so I've distilled my code down to a 
minimal example in the hope that some one can tell me how to fix it.

My package layout is:
package/
  |- setup.py
  |- mytest/
  |- __init__.py
  |- test.py


where the files setup.py, __init__.py and test.py are as follows:

*setup.py*
from setuptools import setup
setup(name='mytest', packages=['mytest'])

*__init__.py*
from __future__ import absolute_import
from .test import atest
from mytest import *

*test.py*
def atest():
print 'A working test'

To install this "package" you can either use plain setup tools with

sage setup.py install

but I decided to pip instead, installing it "locally" and in development mode 
with:

sage -pip install -e --user .

This works fine in that I can start sage and import and use the package, 
but not quite as easily as I'd like:

sage: import mytest
sage: mytest.atest()
A working test
sage: atest()
---
NameError Traceback (most recent call last)
 in ()
> 1 atest()

NameError: name 'atest' is not defined
sage: from mytest import atest  # manually import atest
sage: atest()
A working test

I thought that `atest` would be automatically available from the global 
namespace because of either the second and or the third lines of 
__init__.py. Instead, it still needs to be manually imported. Is there a 
way to put atest into the global namespace when the package is imported?

Of course, it would be even better if the mytest package was automatically 
imported into the global namespace at run-time.

Andrew





-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sagemath-admins] Re: [sage-devel] Re: http://trac.sagemath.org vs https://trac.sagemath.org

[Andrew]

On Wednesday, 8 June 2016 18:03:47 UTC+2, Erik Bray wrote:
>
> On another note, I have a copy of trac.sagemath.org up and running on 
> GCE here: http://104.197.143.230/ 
>
> In the process of setting it up I also upgraded to the latest Trac 
> version (1.1.6).  If anyone has a minute please give it a look and see 
> if anything seems amiss (the data itself is a couple days old). 
>

I had a quick look and everything that I checked for was there. Perhaps 
this has not been configured yet, but I was unable to log on and when I 
tried I got the following error:

Oops… 
Trac detected an internal error: AttributeError: 'FakeSession' object has no 
attribute 'authenticated'
 
There was an internal error in Trac. It is recommended that you notify your 
local Trac administrator with the information needed to reproduce the issue. 

To that end, you could 

 a ticket. 

The action that triggered the error was: GET: /login
 
TracGuide <http://104.197.143.230/wiki/TracGuide> — The Trac User and 
Administration Guide 


Andrew
 



 

 TracGuide <http://104.197.143.230/wiki/TracGuide> — The Trac User and 
Administration Guide 


 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: content of polynomials

[Andrew]

On Thursday, 19 May 2016 19:19:30 UTC+10, Simon King wrote:
>
> Are you using Sage only interactively, or are you also writing programs? 
>
>
Both Simon. Most editors are quite easy to configure to use tab-completion 
as well. I recommend it.

Andrew 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: content of polynomials

[Andrew]

I also vote for 3: command/method names should be as meaningful as 
possible, especially since tab-completion means that no one ever needs to 
type long names. (Short-hands such as and `gens` for generators drive me 
nuts:)

The name `content` doesn't meet this aim but `content_ideal` does.

On Wednesday, 18 May 2016 19:27:22 UTC+10, mmarco wrote:
>
> I vote for 3
>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Finding the right place to edit code

[Andrew]

This is in a part of sage that I never use so I am not qualified to comment 
on what is best usage (and I don't really care:), but changing the default 
behaviour of a function or method should not really be done without some 
form of depreciation warning, so you probably should look at 
`DeprecatedFunctionAlias` in the reference manual.

Secondly, using `besselexpand=True` will be better than using a string.

Andrew

On Tuesday, 10 May 2016 14:48:01 UTC+10, saad khalid wrote:
>
> So, I've set the besselexpand option to true in the init_code of 
> maxima_lib. I was thinking, however, that it would be a good idea to have 
> an easy way to turn besselexpand off, so that those who Want the bessel 
> version of the output can easily get it. This is where I'm running into 
> some issues, I'm not really sure what the best course of action would be. 
> First, I was thinking that I could try to edit the code for sum in 
> calculus.py and maxima_lib.py. I was thinking that, if I added another 
> input variable to symbolic_sum in calculus.py, something like 
> besselexpand='true'. So, the function would look like 
> symbolic_sum(expression, v, a, b, algorithm='maxima',besselexpand='true')
>
> Then, the value for besselexpand could be fed into the call to 
> maxima.sr_sum, and the code could be edited there to let it change the 
> init.code to set besselexpand to false. Ideally, I could add code to 
> symbolic_sum in calculus.py that lets me change the init.code from there, 
> but I don't think that's possible(or rather, I don't know of how to do 
> that). Even with this, however, I can't figure out how to let the function 
> sr_sum change the init.code to set besselexpand to false from within the 
> function. 
>
> Another issue is whether this would even be useful at all, to add this 
> option within sum. I'm assuming there are other situations in which the 
> bessel function appears as output apart from just the sum function? If 
> that's the case, then what I really need is a easy global way to change the 
> setting on besselexpand, and then a good place to document it. I'm new to 
> this, so I would really appreciate everyones thoughts. 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: how we develop sage

[R. Andrew Ohana]

On Tue, Apr 12, 2016 at 12:50 PM, kcrisman  wrote:

>  It doesn't mean that the normal visible
>> public API of Sage changes
>> at all.   Why do you think otherwise?
>>
>
> Well, reading this thread made me think that.  Because I don't see how we
> enforce all those "other pieces" working nicely together, so some would
> (perhaps quite quickly) drop by the wayside.  You are right, as I
> apparently didn't make clear, that it would be even better to have people
> more easily able to have separate packages that are quite narrow - and I
> think that a testing framework like R has would probably suffice for this
> (as long as breaking such packages was a blocker for release!).  (There's
> also the CRAN versus RForge etc. question...) But I don't see how this is
> possible with the *current* Sage.
>
> > Cars are built out of parts.
>
> Yes, parts that are, despite parts suppliers not being the same as the car
> companies, those parts have high tolerances and highly controlled supply
> chains.  (Or so my brief experience with a parts supplier long ago
> suggests.)  All your examples of "mature open source development" are not
> the same in their goal as Sage, which apparently aims to have all of
> mathematics at its fingertips (in the way that Maple and Mathematica,
> though presumably not Magma or Matlab, seem to).
>

This also seems to be the crux of why some Sage developers are not
interested in breaking things up (as opposed to why they actively do not
want to break things up) -- namely that Sage should be a monolithic
application just like the Maple and Mathematica, and that is all it should
be.

While in the early days a lot of Sage's functionality was simply wrapping
other open source libraries, now there is quite a bit that can only be
found in Sage's library -- it seems to me only like the right thing to do
to make it so that others in the open source community could easily benefit
from our work just like we have benefited from theirs.

This doesn't conflict with our mission statement, as it is still perfectly
possible to create a interactive shell with tons of functionality from a
collection of libraries (again, Sage started as this).

As for the technical concerns of having a modular library, it seems the
biggest worry is that it will be too hard to orchestrate all of the
inter-dependent components of Sage. At this point, I'm not too concerned on
this front -- many projects in the past have solved these sorts of issues
and I don't think Sage is special in this regard. I would want to see a
more formal technical proposal (something along the lines of a SEP) before
I would feel comfortable criticizing such a proposal.


> That's a lot harder to disentangle than the dozen or more R packages I've
> had occasion to use are, and presumably also the case in non-mathematical
> software.  Modularity in Sage and resolving our import fiasco isn't the
> same thing as saying that every folder in Sage has to be a separate
> project, which is what you seem to be implying; though since I
> misunderstood the very first point, maybe I'm wrong about that too.
>
> As an example, take game_theory.  This is exactly the kind of "narrow"
> thing one might think would survive better as a modular bit that could be
> imported.  Which one of the programs in question it relies on (gambit) is,
> in terms of Python, of course.  Yet there is a lot of opportunity with
> being inside of "real" Sage for them with interconnections with all kinds
> of other combinatorial and plotting and other stuff that they would be hard
> put to keep current without being in the Sage library.  Having access to
> all that other math makes the game_theory stuff more powerful.  I am
> skeptical that math can be pared down to just a few pieces that everything
> else fairly loosely holds fast to.
>
> But like I said, if you or ODK or someone else can make this vision
> happen, as long as the end user still gets the kitchen sink without having
> to do some wacky import yoga or use possibly-broken packages, I'm not
> complaining!  "I also don't have a problem with things like psage or any
> other such packages" - and if you're right that my view on that is
> selection bias, I would be very happy to be wrong.  (Well, not really that
> happy, because people have worked hard and Sage has had weird upgrades that
> broke their stuff.  But you know what I mean.)  Bring on the automated
> testing!  :-)
>
> --
> 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.
> 

[sage-devel] Re: The Sage Project (Nathann Cohen)

[Andrew]

I sat by and watched the previous thread develop with disbelief but without 
saying anything, so let me say it now. In the last thread there were a lot 
of negative comments from Nathan and many others trying to reason with him: 
Nathan against the world. I hope that this is not going to be repeated here 
as I thought the whole thread was very destructive. I like Nathan: he's a 
nice guy and he contributes a lot of sage code but I also know that these 
threads have turned quite a few people away from sage. I suggest that we 
agree to disagree and spend our energy on something more important.

Regarding the SMC project, as far as I can see it uses SAGE, legally under 
the GPL, and it fully acknowledges all of the contributions from the sage 
community. Moreover, William has aid that any income generated by the 
company will be used to fund further development. I'm happy with that.

The reality is that sage is currently struggling. I have spent quite a lot 
of time writing sage code. If sage suddenly disappears all of the time that 
I have spent on sage will be lost. So it is very much in my own interests 
for SMC to take off because if it works then my code will be viable for 
longer.

I am fully supportive of the SMC and William's efforts to get it up and 
running.
Andrew

On Friday, 26 February 2016 18:51:20 UTC+11, Nathann Cohen wrote:
>
> Hello William,
>
> I don't think that I disagree with any of the goals you aim at for Sage. I
> certainly don't see anything wrong with your involvement in seeing it come
> true. I don't see anything wrong in the way you embrace the problems you 
> meet on
> the way and try to address them.
>
> My main complaint about it all, is that you seem to think about it as if 
> you
> were still alone in the task. So alone that those who have been developing 
> it
> since you stopped are hardly part of the picture you drew (and that's many
> persons, and that's many years). Two problems that I see:
>
> 1) You expect people to participate to a task, but make by yourself 
> decisions
>which involve all of them. Sometimes without informing them, least of 
> all
>discussing the plan with them.
>
> 2) So doing, and because they are not part of the story, you overlook that 
> they
>could also help better toward what seem urgent to you: they could, if 
> you
>involved them more.
>
> It's like you delegated development to the people here, and now have your 
> hands
> free to do whatever you think needs be done. And so doing, people here who
> contribute to sage (and who grew an interest for turning Sage into the 
> perfect
> math software -- all sides of the question considered) are not invited to 
> step
> on this second terrain, where you still seem to think as if you were alone
> against the world.
>
> About your short description of me: be fair. I do not even understand what 
> you
> mean by 'academic use only' (and I'm fine with the GPL) but yes, I would 
> prefer
> all decisions to be taken democratically. Even the non-technical
> decisions. Having sagemath.com redirect elsewhere than sagemath.org was 
> one of
> them. Creating a for-profit company with the same name as the software was
> another.
>
> "With idealistic goals of purity": be fair. I request more democratic 
> decisions,
> and if there is *anything* you can grant me it is the very clear knowledge 
> that
> my opininions are not always shared by everybody. When I ask for more 
> democratic
> decisions, I am sharply aware of the differences. But more democracy, 
> indeed,
> would be an improvement.
>
> "it's ethically wrong to make a release of Sage with known bugs!": be 
> fair. I
> fixed too many of them to believe that I never add any, or that none
> remains. What was ethically wrong in the instance you are apparently 
> refeering
> to was the *removal of a warning* from a code that we knew returned wrong
> results.
>
> Finally: I don't see this project achieving the aim you defined without 
> somebody
> like you. You have the devotion, the energy, the talent. As a human
> being, however, I find it hard to contribute to Sage if you see it as a
> relatively unimportant subtask of a bigger plan over which the
> community has no claim.
>
> Have fun,
>
> Nathann
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] no 7.0 binary for mac

[Andrew Pennebaker]

The SageMath homepage seems to say that v7.0 is available:

http://www.sagemath.org/

But when I try to download the binary for Mac OS X, no download is listed 
for 7.0, just 6.10.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] infinite recursion error during sage compilation

[Andrew Pennebaker]

After `brew cask install sage`, the resulting sage install complains that 
it didn't compile properly.

$ brew cask install sage
...

$ sage
RuntimeError: maximum recursion depth exceeded during compilation
┌┐
│ SageMath Version 6.10, Release Date: 2015-12-18│
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.│
└┘
The Sage installation tree has moved
from 
/Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma
  to 
/opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage
Updating various hardcoded paths...
(Please wait at most a few minutes.)
DO NOT INTERRUPT THIS.
Done updating paths.
Traceback (most recent call last):
  File 
"/opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage/src/bin/sage-ipython",
 
line 8, in 
from sage.repl.readline_extra_commands import *
ImportError: 
dlopen(/opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sage/repl/readline_extra_commands.so,
 
2): Library not loaded: 
/Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma/local/lib/libreadline.6.dylib
  Referenced from: 
/opt/homebrew-cask/Caskroom/sage/6.10/SageMath-6.10.app/Contents/Resources/sage/local/lib/python2.7/site-packages/sage/repl/readline_extra_commands.so
  Reason: image not found

$ specs brew os
specs --version
0.21

brew --version
Homebrew 0.9.5 (git revision 97159; last commit 2016-02-06)

system_profiler SPSoftwareDataType | grep 'System Version'
System Software Overview:
  System Version: OS X 10.11.3 (15D21)
  System Integrity Protection: Enabled

~$ specs sage brew os
specs --version
0.21

sage --version
RuntimeError: maximum recursion depth exceeded during compilation
SageMath Version 6.10, Release Date: 2015-12-18

brew --version
Homebrew 0.9.5 (git revision 97159; last commit 2016-02-06)

system_profiler SPSoftwareDataType | grep 'System Version'
System Software Overview:
  System Version: OS X 10.11.3 (15D21)
  System Integrity Protection: Enabled

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] https on the wiki

[R. Andrew Ohana]

On Wed, Jan 20, 2016 at 5:27 PM, William Stein  wrote:

> Hi,
>
> I thought about this some more today: I personally have zero interest
> or time for personally running wiki.sagemath.org anymore.  It's just
> been coasting for the last year or two.  The moment some spammer takes
> it over, the UW would just take it offline.   The only ways forward
> are either (1) somebody volunteers to take over running the site, or
> (2) we move to github's wiki pages.
>
> Right now I'm trying to find somebody who even remembers their
> password for sudo ssh on wiki.sagemath.org...
>
> Don't tell me (2) isn't possible.  If nothing else, we could just do a
> static dump of the site which would be hosted as part of
> www.sagemath.org, then start fresh with github (maybe copy over a few
> key things that get used a lot, e.g., upcoming sage days and maybe the
> interacts).
>

For (2), Chris Swenson and I did some experiments [1] a couple years ago
and it worked reasonably well. It is probably a decent place to start for
anyone interested in going in that direction.

[1] https://github.com/swenson/sagewiki


>
>  -- William
>
> On Wed, Jan 20, 2016 at 6:58 AM, William Stein  wrote:
> > On Wed, Jan 20, 2016 at 3:21 AM, mmarco  wrote:
> >> Since wiki.sagemath.org requires login for editing (that is, sending
> the
> >> password through the internet)... ¿shouldn't that be done through https?
> >
> > Yes.
> >
> >> On a related note, the certificate for trac.sagemath.org that I am
> getting
> >> is expired, and self-signed
> >
> > I think it always has been self-signed...
> >
> >> Could we get a certificate (for instance, from www.letsencrypt.org )
> that
> >> doesn't scare people away from using secure connections?
> >
> > That would be great.
> >
> > Are you volunteering to do everything?
> >
> > William
> >
> >>
> >> --
> >> 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 post to this group, send email to sage-devel@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/sage-devel.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > William (http://wstein.org)
>
>
>
> --
> William (http://wstein.org)
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: status on Python3

[R. Andrew Ohana]

At this point it all of sage's dependencies build with python 3, so if you
do the following

SAGE_PYTHON3=yes make

it will fail building some cython module in the sage library.

On Sat, Nov 14, 2015 at 7:45 PM, Nathan Dunfield 
wrote:

> can someone summarize the status on making SageMath Python3 compatible?
>> (...or more provocatively: When will SageMath start using Python3?)
>
>
> See
>
> http://trac.sagemath.org/ticket/15530
>
> and tickets 15980 and 16052 referenced therein.
>
> Best,
>
> Nathan
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: access denied on git

[R. Andrew Ohana]

You are using the read only git url, you need to use the ssh url to be able
to push. You can either add a new remote:

git remote add trac g...@trac.sagemath.org:sage.git

or modify your current remote:

git remote set-url origin g...@trac.sagemath.org:sage.git


On Mon, Sep 21, 2015 at 7:16 PM, Mike Zabrocki 
wrote:

> With some further experimenting I find that I can push from my old copy of
> sage (but I can't compile there).
>
> I can edit and compile on one copy of sage and push with another.  This is
> an awkward setup, but at least I can some edits to a ticket done.
> -Mike
>
>
> On Monday, 21 September 2015 21:57:10 UTC-4, Mike Zabrocki wrote:
>>
>> You are right that running Xcode did install the command line tools, but
>> that did not seem to fix the problem.
>> I continue to get the "fatal: remote error: access denied or repository
>> not exported: /sage.git" message.
>> -Mike
>>
>> On Monday, 21 September 2015 21:21:45 UTC-4, John H Palmieri wrote:
>>>
>>>
>>>
>>> On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote:
>>>>
>>>> I mistakenly installed XCode 7 and so to save myself I started working
>>>> on a fresh copy of sage where I don't do too much compiling.
>>>>
>>>
>>> Have you tried running Xcode once? It will install some command-line
>>> tools, and that may be what is necessary.
>>>
>>>   John
>>>
>>>
>>>
>>>
>>>>
>>>> In doing so I seem to have messed up my permissions to access git (or
>>>> something).  I can checkout any branch I like, but I can't seem to push.
>>>>
>>>> $ git push
>>>>
>>>> fatal: remote error: access denied or repository not exported: /sage.git
>>>>
>>>> I thought it might be my ssh key, but I can authenticate:
>>>>
>>>> $ ssh g...@trac.sagemath.org info
>>>>
>>>> hello zabrocki, this is git@trac running gitolite3 (unknown) on git
>>>> 1.7.9.5
>>>>
>>>>
>>>>  R W sage
>>>>
>>>> Does anyone have an idea about what I am doing wrong?
>>>>
>>>> Thanks.
>>>> -Mike
>>>>
>>> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: *.math.washington.edu hardware resources

[R. Andrew Ohana]

I just updated the project with some excel + csv files with a much more
indepth inventory.

Also, concerning ansible -- this is what I used when working on things this
summer (see https://github.com/ohanar/sagemath.org). I found that when you
use any well supported plugin, using ansible was very pleasant, but once
you stepped outside of the ecosystem -- it got to be a pain very quickly. A
lot of this can be solved by writing your own plugins, but I found that to
also have quite a learning curve (ansible does some python magic that
defines various global variables in your modules).

An alternative to look at is saltstack -- it is also written in python, and
also uses yaml as its primary configuration format. I've heard writing
plugins for it is simpler as well, but I haven't investigated it thoroughly.

On Wed, Sep 16, 2015 at 2:08 PM, kcrisman  wrote:

>
>
> Please try to understand, once again, that you are at CNRS in a very
>> fortunate and exceptional position, and many people are much less
>> lucky. Try to get a grant and manage it to see my point :-)
>>
>>
>>
> And (not speaking to Nathann or anyone else) try it when teaching a 3-3 or
> 4-4 load at a place where teaching by far is the main component to
> tenure... I am hoping that more and more of them will do like Greg Bard did
> and write a Sage teaching book, but that will take time (and maybe MBX!).
> But for developing it's a real challenge to find that reliable time.
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: *.math.washington.edu hardware resources

[R. Andrew Ohana]

As William mentioned, I don't really have the time to work on administering
the cluster, but I would be happy to part of the initial discussions (e.g
what I was planning on doing if I had the time, why I chose centos,
in-depth inventory of hardware, etc).

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Please redirect the old homepage of my cohomology spkg

[R. Andrew Ohana]

Sage.math points to wstein.org (as per an earlier request by William). As
far as I'm aware, he is the only one with credentials to that system, I
certainly don't have access.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Access to my cohomology spkg&documentation is blocked

[R. Andrew Ohana]

Everybody was warned that things would go down back in April, so you should
have dealt with it awhile ago (but apparently didn't).

We can easily setup a redirect on the VM that hosts wstein.org (which is
where sage.math.washington.edu redirects to) if you find a place to host
your site. If your site is too big to host on github or the like, and we
can setup a vm for it (assuming your site falls within what is allowed by
the UW). If you need to get files, you can still access your home directory
from geom.math.washington.edu or comhinat.math.washington.edu.

(The same goes for anyone else who hosted things off of boxen.)

On Fri, Aug 28, 2015 at 02:15 Simon King  wrote:

> Hi!
>
> It was pointed out on sage-support that
> http://sage.math.washington.edu/home/SimonKing/Cohomology/
> is not available. That's bad, because the documentation of my
> optional group cohomology spkg is hosted there, the new
> to-be-reviewed version of the spkg is hosted there (I am afraid
> that the old versions would not work, because of backward incompatible
> changes in Sage), and as soon as I change the spkg to the new format,
> the upstream sources will be hosted there (at least I think it would
> be a logical place).
>
> How can that be solved? I don't think hosting it in Jena is a solution,
> since I am about to move to Cologne.
>
> Best regards,
> Simon
>
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Trac vs Wiki passwords

[R. Andrew Ohana]

On Mon, Aug 24, 2015 at 6:25 AM, kcrisman  wrote:

>
>>> trac and wiki accounts used to be linked (same username, same password).
>>> I
>>> changed my password on trac and it worked, but i can not use it on the
>>> wiki. Unfortunately, i am travelling and i do not have access to my
>>> previous password. How are the two system currently related ?
>>>
>>
>> Not at all. You can't currently change your wiki password. Basically
>> through a series of hacks, we had hooked the wiki's authentication up to
>> trac, but I think that broke when the wiki was moved off of boxen last
>> summer.
>>
>>
> Oh, was that heavily advertised?  I think we probably still have quite a
> bit of documentation that says both have the same password...
>

It was probably an oversight. I only realized that this was the case within
the last week or so.


>
>
>
>> On a slight tangent: I personally don't care for our current wiki,
>> MediaWiki -- it has caused us numerous issues over the years (e.g. memory
>> hog on boxen), and is a bit of a pain to administer. I'm not really aware
>> of any modern wiki platforms (other than gollum, which didn't handle large
>> wikis like ours when I checked it out 1.5 years ago), but if anyone has any
>> thoughts on the matter I would be happy to discuss it (maybe in a different
>> thread).
>>
>
> I don't know that moving all that content/links would be worth the effort.
>

We could setup a redirect, or apply a regex during such a transition, so
changing links is not really an issue. Moving content is worthwhile if it
is a noticeable reduction in maintenance.

> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Trac vs Wiki passwords

[R. Andrew Ohana]

On Sat, Aug 22, 2015 at 10:07 PM, William Stein  wrote:

> On Sat, Aug 22, 2015 at 8:55 PM, R. Andrew Ohana 
> wrote:
> >
> >
> > On Sat, Aug 22, 2015 at 4:22 AM, Thierry <
> sage-googlesu...@lma.metelu.net>
> > wrote:
> >>
> >> Hi,
> >>
> >> trac and wiki accounts used to be linked (same username, same
> password). I
> >> changed my password on trac and it worked, but i can not use it on the
> >> wiki. Unfortunately, i am travelling and i do not have access to my
> >> previous password. How are the two system currently related ?
> >
> >
> > Not at all. You can't currently change your wiki password. Basically
> through
> > a series of hacks, we had hooked the wiki's authentication up to trac,
> but I
> > think that broke when the wiki was moved off of boxen last summer.
> >
> > On a slight tangent: I personally don't care for our current wiki,
> MediaWiki
> > -- it has caused us numerous issues over the years (e.g. memory hog on
> > boxen), and is a bit of a pain to administer. I'm not really aware of any
> > modern wiki platforms (other than gollum, which didn't handle large wikis
> > like ours when I checked it out 1.5 years ago), but if anyone has any
> > thoughts on the matter I would be happy to discuss it (maybe in a
> different
> > thread).
>
> What about
>
> https://github.com/sagemath/sage/wiki


Github's wiki is gollum.


>
>
> William
>
> >
> >>
> >>
> >> Ciao,
> >> Thierry
> >>
> >> --
> >> 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 post to this group, send email to sage-devel@googlegroups.com.
> >> Visit this group at http://groups.google.com/group/sage-devel.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> >
> > --
> > Andrew
> >
> > --
> > 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 post to this group, send email to sage-devel@googlegroups.com.
> > Visit this group at http://groups.google.com/group/sage-devel.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> William (http://wstein.org)
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Trac vs Wiki passwords

[R. Andrew Ohana]

On Sat, Aug 22, 2015 at 4:22 AM, Thierry 
wrote:

> Hi,
>
> trac and wiki accounts used to be linked (same username, same password). I
> changed my password on trac and it worked, but i can not use it on the
> wiki. Unfortunately, i am travelling and i do not have access to my
> previous password. How are the two system currently related ?
>

Not at all. You can't currently change your wiki password. Basically
through a series of hacks, we had hooked the wiki's authentication up to
trac, but I think that broke when the wiki was moved off of boxen last
summer.

On a slight tangent: I personally don't care for our current wiki,
MediaWiki -- it has caused us numerous issues over the years (e.g. memory
hog on boxen), and is a bit of a pain to administer. I'm not really aware
of any modern wiki platforms (other than gollum, which didn't handle large
wikis like ours when I checked it out 1.5 years ago), but if anyone has any
thoughts on the matter I would be happy to discuss it (maybe in a different
thread).


>
> Ciao,
> Thierry
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] trac authentication failures

[R. Andrew Ohana]

Password reset on our trac instance doesn't work (and I have looked into it
a few times and haven't been able to figure out why it is broken).

I can create a temporary password for you manually and send it to you (at
which point you should be able to change your password from your user
preferences without issue).


On Fri, Aug 21, 2015 at 3:35 PM, AlexGhitza  wrote:

> Hi,
>
> I tried logging into trac today after a long time away, and failed.
> Thinking that I had just forgotten my password, I asked for a password
> reset, and then retried with the automatically generated password that trac
> emailed me.  Still getting an authentication failure.
>
> Thoughts?
>
>
> Best,
> Alex
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] trac chronic health problem

[R. Andrew Ohana]

There was a cron job setup for cleaning /tmp, but I just looked and it
seems like it was disabled... I re-enabled it and manually cleaned it at
the same time.

On Sun, Aug 16, 2015 at 6:48 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:

> Hello,
>
> Again...
>
> """
> Trac detected an internal error:
>
> OSError: [Errno 2] No such file or directory: '/tmp/tmpVRSiHH'
> """
>
> Wouldn't be possible to set a cron job cleaning /tmp/?
>
> Vincent
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Trac Server Issue

[R. Andrew Ohana]

This should now be resolved.

On Sun, Aug 16, 2015 at 6:10 PM, Kwankyu Lee  wrote:

> I looked into this thread because I have the same issue with the following
> ticket.
>
> http://trac.sagemath.org/ticket/18807
>
> Anyway, your ticket URL seems to have no 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Patchbot reporting failed builds: Zorn

[Andrew Gainer-Dewar]

Honestly, I'm not entirely sure what the problem was. I killed the
patchbot, did a 'make clean && make doc-clean && git checkout develop &&
make', and then fired it back up, and things seem to be working now.

On Thu, Aug 13, 2015 at 10:12 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:

> We should try to make the patchbot safer to such building failures...
> Andrew, could you give us more details about what was going wrong?
>
>
> On 13/08/15 16:09, Nathann Cohen wrote:
>
>> Thanks !
>>
>> Nathann
>>
>> On 13 August 2015 at 16:07, Andrew Gainer-Dewar
>>  wrote:
>>
>>> Whoops! I think everything is fixed now. Sorry about the mess.
>>>
>>> --Andrew
>>>
>>>
>>> On Thursday, August 13, 2015 at 5:16:03 AM UTC-4, vdelecroix wrote:
>>>
>>>>
>>>> Seems to be agd, see
>>>>
>>>> http://wiki.sagemath.org/buildbot/owners
>>>>
>>>> And trac says Andrew Gainer-Dewar.
>>>>
>>>> On 13/08/15 09:34, Nathann Cohen wrote:
>>>>
>>>>> Hello everybody,
>>>>>
>>>>> Is the owner of 'Zorn' reading this mailing list? The machine reports
>>>>> a build failure on a ticket, and I do not think that the errors are
>>>>> related:
>>>>>
>>>>> http://trac.sagemath.org/ticket/19018
>>>>>
>>>>> Here is the bottom of the shortlog
>>>>>
>>>>> -
>>>>> * package: Cython
>>>>> log file:
>>>>> /mnt/pile/data/servers/sage/sage-patchbot/logs/pkgs/Cython.log
>>>>> build directory:
>>>>>
>>>>>
>>>>> /mnt/pile/data/servers/sage/sage-patchbot/local/var/tmp/sage/build/Cython
>>>>>
>>>>> * package: gp2c
>>>>> log file:
>>>>> /mnt/pile/data/servers/sage/sage-patchbot/logs/pkgs/gp2c.log
>>>>> build directory:
>>>>> /mnt/pile/data/servers/sage/sage-patchbot/local/var/tmp/sage/build/gp2c
>>>>>
>>>>> * documentation: dochtml
>>>>> log file:
>>>>> /mnt/pile/data/servers/sage/sage-patchbot/logs/pkgs/../dochtml.log
>>>>> ---
>>>>>
>>>>> Nathann
>>>>>
>>>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "sage-devel" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/sage-devel/tQFsu-LWto0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> sage-devel+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/tQFsu-LWto0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Patchbot reporting failed builds: Zorn

[Andrew Gainer-Dewar]

Whoops! I think everything is fixed now. Sorry about the mess.

--Andrew

On Thursday, August 13, 2015 at 5:16:03 AM UTC-4, vdelecroix wrote:
>
> Seems to be agd, see 
>
> http://wiki.sagemath.org/buildbot/owners 
>
> And trac says Andrew Gainer-Dewar. 
>
> On 13/08/15 09:34, Nathann Cohen wrote: 
> > Hello everybody, 
> > 
> > Is the owner of 'Zorn' reading this mailing list? The machine reports 
> > a build failure on a ticket, and I do not think that the errors are 
> > related: 
> > 
> > http://trac.sagemath.org/ticket/19018 
> > 
> > Here is the bottom of the shortlog 
> > 
> > - 
> > * package: Cython 
> >log file: 
> /mnt/pile/data/servers/sage/sage-patchbot/logs/pkgs/Cython.log 
> >build directory: 
> > 
> /mnt/pile/data/servers/sage/sage-patchbot/local/var/tmp/sage/build/Cython 
> > 
> > * package: gp2c 
> >log file: 
> /mnt/pile/data/servers/sage/sage-patchbot/logs/pkgs/gp2c.log 
> >build directory: 
> > /mnt/pile/data/servers/sage/sage-patchbot/local/var/tmp/sage/build/gp2c 
> > 
> > * documentation: dochtml 
> >log file: 
> /mnt/pile/data/servers/sage/sage-patchbot/logs/pkgs/../dochtml.log 
> > --- 
> > 
> > Nathann 
> > 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: William Stein - CEO, SageMath, Inc. http://sagemath.com

[Andrew]

I strongly agree with Dima. My understanding is that SageCloud is NOT a 
money making venture but rather a means of supporting sage. IMHO it's a 
good thing and I am happy for my code to go there (not that I have time to 
write much at present:().

Andrew

On Thursday, 13 August 2015 08:02:58 UTC+10, Dima Pasechnik wrote:
>
>
>
> On Wednesday, 12 August 2015 10:55:45 UTC-7, Nathann Cohen wrote:
>>
>> Hello William, 
>>
>> I cannot say that I like your new signature the slightest bit [1]. 
>>
>> I feel like the work to software I contribute is being stolen by 
>> somebody who wants to make money off it. I feel like its name has been 
>> stolen too. Sagemath is clearly a free software for mathematics, and 
>> "Sagecloud" can pass for being something something different. 
>>
>> But when sagemath.com is a website that sells Sage Cloud, we have a 
>> problem.  
>>
>
> the point of selling Sage Cloud is  to fund development of Sagemath.
> William, please shout if I get it wrong, and you actually gold-plate 
> your skateboards using proceeds from Sage Cloud... 
>
> Nathann, if you know other means novel means to fund this, please share...
>
>
>
>> Regards, 
>>
>> Nathann 
>>
>> [1] https://groups.google.com/d/msg/sage-cloud/31raOrutcog/DkKI2wGKCAAJ 
>>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Trac notifications (was Re: Mutability of matrices with no entries)

[R. Andrew Ohana]

On Aug 1, 2015 13:21, "Michael Orlitzky"  wrote:
>
> On 07/31/2015 07:51 PM, Andrey Novoseltsev wrote:
> > Hello,
> >
> > While working on http://trac.sagemath.org/ticket/18613 I ran into the
> > following problem:
>
> Argh, the trac notifications still aren't fixed. Can someone please add
> a reverse DNS entry for 128.208.160.253 (the server that's sending the
> notifications)? The PTR should be "trac.sagemath.org" since that's the
> name the server is saying "HELO" with.

I've made a request to UW to add the DNS entry (since they are effectively
our ISP), but they like to take their time. I finally got a response on the
ticket I opened last night, so hopefully this will be resolved soon.

>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: no trac mail notifications?

[R. Andrew Ohana]

Trac's ip address changed on Saturday, which that might have broken
something with the email signature. I'll take a look later today.
On Jul 20, 2015 10:27, "Benjamin Hackl"  wrote:

> Our mail system alters the subject (probably since today; wasn't like that
> last Thursday) like this:
>
> ***EVENTUELL*SPAM*** [4.979 / 4] Re: [sage-trac]
>
> Maybe this helps someone.
>
> All the best,
> Benjamin
>
> Am Montag, 20. Juli 2015 19:21:15 UTC+2 schrieb Daniel Krenn:
>>
>> Am 2015-07-20 um 19:08 schrieb Benjamin Hackl:
>> > ... might be just here at AAU. I found my notifications in the spam
>> folder.
>>
>> I do not use the @aau.at address.
>>
>> Could there have been changes in trac's mails so that some servers do
>> not accept the mails (or declare them as spam)?
>>
>>  --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Server Relocation

[R. Andrew Ohana]

Most of these sites should now be back up. The patchbot still needs a
little bit of setup (from Robert and Frederic), so it will be down until
they have a chance to look at it.

On Sat, Jul 18, 2015 at 9:26 AM, William Stein  wrote:

>
>
> On Friday, July 17, 2015, R. Andrew Ohana  wrote:
>
>> Small update, we will be starting at around 8 AM PST tomorrow.
>>
>> On Sat, Jul 11, 2015 at 18:40 R. Andrew Ohana 
>> wrote:
>>
>>> Due to lack of funding (as previously mentioned by William), the servers
>>> that are currently hosting a number of the sagemath sites will need to be
>>> relocated. We are currently planning on doing this next Saturday (i.e.
>>> Saturday July 18), exactly when and for exactly how long is not quite
>>> clear, but you can probably expect things to be down for a few hours.
>>>
>>> List of sagemath sites that will be down:
>>>
>>> trac.sagemath.org
>>> git.sagemath.org
>>> wiki.sagemath.org
>>> files.sagemath.org
>>> files.old.sagemath.org
>>> patchbot.sagemath.org
>>>
>>>
>>> In addition, boxen.math.washington.edu will finally be going offline,
>>> and due to lack of space won't be coming back (at least for now). I am
>>> working on setting up a new cluster of machines for sage development (and
>>> for math research a little later down the road) using the old SMC cluster
>>> (which consists of around 20 machines).
>>>
>>>
>>>
>>> --
>>> Andrew
>>>
>>  --
>> 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 post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Sent from my massive iPhone 6 plus.
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Server Relocation

[R. Andrew Ohana]

Small update, we will be starting at around 8 AM PST tomorrow.

On Sat, Jul 11, 2015 at 18:40 R. Andrew Ohana 
wrote:

> Due to lack of funding (as previously mentioned by William), the servers
> that are currently hosting a number of the sagemath sites will need to be
> relocated. We are currently planning on doing this next Saturday (i.e.
> Saturday July 18), exactly when and for exactly how long is not quite
> clear, but you can probably expect things to be down for a few hours.
>
> List of sagemath sites that will be down:
>
> trac.sagemath.org
> git.sagemath.org
> wiki.sagemath.org
> files.sagemath.org
> files.old.sagemath.org
> patchbot.sagemath.org
>
>
> In addition, boxen.math.washington.edu will finally be going offline, and
> due to lack of space won't be coming back (at least for now). I am working
> on setting up a new cluster of machines for sage development (and for math
> research a little later down the road) using the old SMC cluster (which
> consists of around 20 machines).
>
>
>
> --
> Andrew
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Server Relocation

[R. Andrew Ohana]

On Sun, Jul 12, 2015 at 6:02 AM, Jeroen Demeyer 
wrote:

> On 2015-07-12 03:40, R. Andrew Ohana wrote:
>
>> In addition, boxen.math.washington.edu
>> <http://boxen.math.washington.edu> will finally be going offline, and
>> due to lack of space won't be coming back (at least for now).
>>
>
> Important question: what will happen with the data currently stored on
> boxen? Will you transfer it to the new machine?
>

It depends on what you mean by data currently on boxen. Do you mean things
under /home? If so then that will still be accessible on
geom.math.washington.edu and mod.math.washington.edu for the time being, as
it actually a network filesystem being exported from another machine.

My plan is to mount it as read only for a bit on the new machines, but
after a period of time (probably a couple of months) the storage machine of
the current/old sage cluster will be repurposed as a backup machine, at
which point I'll make a final snapshot of the /home directory on an
external usb drive.


Anything lying on the root and scratch filesystems on boxen will be wiped.


> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Server Relocation

[R. Andrew Ohana]

Due to lack of funding (as previously mentioned by William), the servers
that are currently hosting a number of the sagemath sites will need to be
relocated. We are currently planning on doing this next Saturday (i.e.
Saturday July 18), exactly when and for exactly how long is not quite
clear, but you can probably expect things to be down for a few hours.

List of sagemath sites that will be down:

trac.sagemath.org
git.sagemath.org
wiki.sagemath.org
files.sagemath.org
files.old.sagemath.org
patchbot.sagemath.org


In addition, boxen.math.washington.edu will finally be going offline, and
due to lack of space won't be coming back (at least for now). I am working
on setting up a new cluster of machines for sage development (and for math
research a little later down the road) using the old SMC cluster (which
consists of around 20 machines).


-- 
Andrew

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.