[sage-release] Re: Sage 7.5.beta5 released

2016-12-05 Thread Kwankyu Lee
I just noticed sage$: sage -t src/sage/rings/function_field/* ... ValueError: unknown file extension '.pyc' This worked fine previously... -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving

[sage-release] Re: Sage 7.5.beta5 released

2016-12-02 Thread John H Palmieri
On Friday, December 2, 2016 at 7:22:05 AM UTC-8, John H Palmieri wrote: > > Just for kicks, I tried building with SAGE_CHECK=yes. (Do any of the > buildbots do this?) > > On two different OS X machines, 10.11 and 10.12, two : > The end of this should have said "two packages failed their

[sage-release] Re: Sage 7.5.beta5 released

2016-12-02 Thread John H Palmieri
Just for kicks, I tried building with SAGE_CHECK=yes. (Do any of the buildbots do this?) On two different OS X machines, 10.11 and 10.12, two : Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all'): * package: cython-0.25.1.p0

[sage-release] Re: Sage 7.5.beta5 released

2016-12-01 Thread Sébastien Labbé
> > make ptestlong creates two sage.png file due to #21947 (I will create a > ticket to fix this shortly) > https://trac.sagemath.org/ticket/22009 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop

[sage-release] Re: Sage 7.5.beta5 released

2016-12-01 Thread Paul Masson
The develop branch now has two uncommitted files, both with the first line: # This file is auto-generated by sage_setup/autogen/pari/generator.py On Thursday, December 1, 2016 at 3:15:57 PM UTC-8, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git >