[sage-release] Re: Sage 8.1.rc0 released

On Friday, November 17, 2017 at 10:40:22 AM UTC-8, Simon King wrote: > > Hi John, > > On 2017-11-17, John H Palmieri wrote: > >> And WHY that change was made! > >> > > > > If it takes a while to build the documentation, better to start as soon > as > > possible,

[sage-release] Re: Sage 8.1.rc0 released

Hi John, On 2017-11-17, John H Palmieri wrote: >> And WHY that change was made! >> > > If it takes a while to build the documentation, better to start as soon as > possible, rather than to wait until the last possible time, right? If the user's purpose is to use Sage,

Re: [sage-release] Re: Sage 8.1.rc0 released

On 2017-11-17 14:51, Kwankyu Lee wrote: This (building the documentation is no longer the last step) sounds a big change to me. I wonder when that change was made. In Sage 6.8, see https://trac.sagemath.org/ticket/18710 -- You received this message because you are subscribed to the Google

[sage-release] Re: Sage 8.1.rc0 released

On Friday, November 17, 2017 at 6:37:54 AM UTC-8, Simon King wrote: > > On 2017-11-17, Kwankyu Lee wrote: > > Ah, I didn't know that. This (building the documentation is no longer > the > > last step) sounds a big change to me. I wonder when that change was > made. > >

[sage-release] Re: Sage 8.1.rc0 released

On 2017-11-17, Thierry wrote: > On Fri, Nov 17, 2017 at 02:37:37PM +, Simon King wrote: > >> Is it still possible to build SageMath without documentation ("make start")? > > make build Thanks! -- You received this message because you are subscribed

Re: [sage-release] Re: Sage 8.1.rc0 released

On Fri, Nov 17, 2017 at 02:37:37PM +, Simon King wrote: > Is it still possible to build SageMath without documentation ("make start")? make build Ciao, Thierry -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from

Re: [sage-release] Re: Sage 8.1.rc0 released

Hi, Le vendredi 17 novembre 2017 15:15:13 UTC+1, Kwankyu Lee a écrit : > > > Is this normal situation? This betrays my belief that a command like > > $ sage -t src/sage/rings/finite_rings/* > > always works fine. > > You should use instead sage -t src/sage/rings/finite_rings/ (skip the *) Best

Re: [sage-release] Re: Sage 8.1.rc0 released

I noticed this: $ sage -t src/sage/rings/finite_rings/* Running doctests with ID 2017-11-17-23-04-49-f065787a. Git branch: finite_field_extension_trac24195_dev Using --optional=mpir,python2,sage Traceback (most recent call last): File "/Users/Kwankyu/GitHub/sage/src/bin/sage-runtests", line

Re: [sage-release] Re: Sage 8.1.rc0 released

On Friday, November 17, 2017 at 6:53:41 PM UTC+9, Thierry wrote: > > > How much available RAM do you have ? Building the documentation is no > longer the last step, hence if that fails, everything after that is not > built. Ah, I didn't know that. This (building the documentation is no

Re: [sage-release] Re: Sage 8.1.rc0 released

Hi, On Thu, Nov 16, 2017 at 05:05:11PM -0800, Kwankyu Lee wrote: [...] > There was an error in building doc. I ignored this as there was no problem > in running Sage. > How much available RAM do you have ? Builging the documentation is no longer the last step, hence if that fails, everything

Re: [sage-release] Re: Sage 8.1.rc0 released

On 2017-11-17 02:05, Kwankyu Lee wrote: There was an error in building doc. There you have it! The build didn't succeed. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send

Re: [sage-release] Re: Sage 8.1.rc0 released

It might be that a dependency is missing somewhere. While building rc1, I had to start make for the 2nd time for no apparent reason. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from

Re: [sage-release] Re: Sage 8.1.rc0 released

On Thursday, November 16, 2017 at 8:38:52 PM UTC+9, Jeroen Demeyer wrote: > > > It seems that sympy simply wasn't built. I am not aware of any bug in > the build system (especially not specific to OS X) which could cause that. > The fresh build (of actually Sage 8.1rc1) finished with no

Re: [sage-release] Re: Sage 8.1.rc0 released

> > Sorry to ask a silly question, but are you sure that > > (1) You actually ran "make" > Yes. But this was not a fresh one. I ran "make distclean", and then "make". > (2) That run of "make" succeeded without errors > There was an error in building doc. I ignored this as there was no

Re: [sage-release] Re: Sage 8.1.rc0 released

On 2017-11-16 07:38, Kwankyu Lee wrote: I get the following just after "make", Sorry to ask a silly question, but are you sure that (1) You actually ran "make" (2) That run of "make" succeeded without errors It seems that sympy simply wasn't built. I am not aware of any bug in the build

Re: [sage-release] Re: Sage 8.1.rc0 released

Then I created a new directory at SAGE_ROOT/src/ext/directory and put a file "test.txt" $ ls -l src/ext/ total 0 drwxr-xr-x 3 Kwankyu staff 102 Nov 16 15:42 directory drwxr-xr-x 4 Kwankyu staff 136 Apr 15 2015 doctest drwxr-xr-x 5 Kwankyu staff 170 Apr 14 2016 gap drwxr-xr-x 3

Re: [sage-release] Re: Sage 8.1.rc0 released

So I ran sage -i sympy and Sage installed sympy. Then now this works fine. $ sage -t src/sage/rings/function_field/* -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [sage-release] Re: Sage 8.1.rc0 released

I get the following just after "make", Hera:sage$ sage -t src/sage/rings/function_field/* Running doctests with ID 2017-11-16-15-36-55-9cd5f354. Git branch: develop Using --optional=mpir,python2,sage Doctesting 8 files. Traceback (most recent call last): File

Re: [sage-release] Re: Sage 8.1.rc0 released

Define strange behaviours? > On 16/11/2017, at 18:52, Kwankyu Lee wrote: > > Hi, > > Does this release support Xcode 9.1 on mac? > > I built this release with Xcode 9.1, and the Sage built shows strange > behaviors. Is this because of Xcode 9.1? -- You received this

[sage-release] Re: Sage 8.1.rc0 released

Hi, Does this release support Xcode 9.1 on mac? I built this release with Xcode 9.1, and the Sage built shows strange behaviors. Is this because of Xcode 9.1? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group

[sage-release] Re: Sage 8.1.rc0 released

Le vendredi 10 novembre 2017 14:42:44 UTC+1, Eric Gourgoulhon a écrit : > > On the same computer as above (Ubuntu 16/04), > ./sage -n > fails with the following error message: > > [C 14:35:42.400 NotebookApp] Bad config encountered during initialization: > [C 14:35:42.400 NotebookApp] The

Re: [sage-release] Re: Sage 8.1.rc0 released

I created https://trac.sagemath.org/ticket/24190 for the issue. On Friday, 10 November 2017 13:34:53 UTC+1, Volker Braun wrote: > > Can somebody open a ticket for that issue? > > On Thursday, November 9, 2017 at 11:44:43 PM UTC+1, François Bissey wrote: >> >> Smells like

[sage-release] Re: Sage 8.1.rc0 released

On the same computer as above (Ubuntu 16/04), ./sage -n as well as any of the equivalent commands ./sage --notebook ./sage -n export ./sage --notebook export fails with the following error message: [C 14:35:42.400 NotebookApp] Bad config encountered during initialization: [C 14:35:42.400

[sage-release] Re: Sage 8.1.rc0 released

Scipy fails to build on the sage4 patchbot (4.4.26-gentoo). Relevant part of the log: [scipy-0.19.1] getarrdims:warning: assumed shape array, using 0 instead of '*' [scipy-0.19.1] getarrdims:warning: assumed shape array, using 0 instead of '*' [scipy-0.19.1]x,y =

Re: [sage-release] Re: Sage 8.1.rc0 released

Can somebody open a ticket for that issue? On Thursday, November 9, 2017 at 11:44:43 PM UTC+1, François Bissey wrote: > > Smells like https://trac.sagemath.org/ticket/23742 > > > On 10/11/2017, at 11:31, John H Palmieri > wrote: > > > > WIth OS X 10.12.6, Xcode (and the

[sage-release] Re: Sage 8.1.rc0 released

On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone + pull develop, parallel (-j16) build OK and ptestlong failed with one doctest: sage -t --long --warn-long 45.7 src/sage/geometry/riemannian_manifolds/surface3d_generators.py # 1 doctest failed As usual on this computer

[sage-release] Re: Sage 8.1.rc0 released

On Debian testing 8.1.rc0 + Trac#24121 in its current state passes ptestlong without error whatsoever. HTH, -- Emmanuel Charpentier Le mercredi 8 novembre 2017 22:30:44 UTC+1, Volker Braun a écrit : > > As always, you can get the latest beta version

Re: [sage-release] Re: Sage 8.1.rc0 released

Yes, I agree, in the sense that the failure is coming from the doctests added there. I just tried the same doctests (without the rest of the changes from #23742) with 8.1.beta8, and the same thing happens. So it looks like #23742 adds doctests but doesn't fully fix the issues that the doctests

Re: [sage-release] Re: Sage 8.1.rc0 released

Smells like https://trac.sagemath.org/ticket/23742 > On 10/11/2017, at 11:31, John H Palmieri wrote: > > WIth OS X 10.12.6, Xcode (and the same happens when building with clang, > #12426): > > sage -t --long --warn-long 64.0 src/sage/matrix/matrix_mod2_dense.pyx # >

[sage-release] Re: Sage 8.1.rc0 released

WIth OS X 10.12.6, Xcode (and the same happens when building with clang, #12426): sage -t --long --warn-long 64.0 src/sage/matrix/matrix_mod2_dense.pyx # Killed due to kill signal ** Tests run before process (pid=12556)