On 2016-07-31 22:21, Simon King wrote:
So, that doesn't seem to work, at least not with the Cython version that
is part of Sage.
Yes, this new build_ext is not yet in any released version, the current
recommendation is to use cythonize().
--
You received this message because you are subscrib
On 2016-07-31 22:01, Simon King wrote:
The pages
http://docs.cython.org/en/latest/src/quickstart/build.html
and
http://docs.cython.org/en/latest/src/reference/compilation.html
tell me to use build_ext.
Don't believe those pages. That's a documentation bug.
--
You received this message be
Simon King wrote:
> Hi Jeroen,
>
> On 2016-07-31, Simon King wrote:
>> On 2016-07-31, Jeroen Demeyer wrote:
>>> The problem is this line in setup.py:
>>>
>>> from Cython.Distutils import build_ext
>>>
>>> This "build_ext" command is an old and semi-broken way to compile Cython
>>> files. In fac
On 01/08/16 09:49, leif wrote:
because this is an old bug (happened in the past with MPIR as well)
which never got fixed nor really tracked down, just the now failing
doctest (unpickling all a second time) got added in #5838; I've also
commented there [1].
-leif
[1] https://trac.sagemath.org/t
leif wrote:
> leif wrote:
>> Currently retrying with GMP 6.1.1 (and GCC 5.4), too; I'll presumably
>> open a ticket to upgrade Sage's GMP package.
>>
>>
>>> The failing doctests are
>>> [...]
>>> sage -t --long
>> /usr/lib64/python2.7/site-packages/sage/rings/integer.pyx # 1 doctest
>> failed
>>>
Hi Jeroen,
On 2016-07-31, Simon King wrote:
> On 2016-07-31, Jeroen Demeyer wrote:
>> The problem is this line in setup.py:
>>
>> from Cython.Distutils import build_ext
>>
>> This "build_ext" command is an old and semi-broken way to compile Cython
>> files. In fact, newer versions of Cython hav
On Sunday, July 31, 2016 at 1:18:11 PM UTC+1, Simon King wrote:
>
> Hi Vincent,
>
> On 2016-07-31, Vincent Delecroix <20100.d...@gmail.com >
> wrote:
> > $ sage -q
>
> What das sage -q do?
>
Das ist "Keine Sage banner" Option :-)
$ sage -advanced | less
...
-q -- quiet; s
Hi Jeroen,
On 2016-07-31, Jeroen Demeyer wrote:
> The problem is this line in setup.py:
>
> from Cython.Distutils import build_ext
>
> This "build_ext" command is an old and semi-broken way to compile Cython
> files. In fact, newer versions of Cython have an improved "build_ext"
> command and g
Hi Vincent,
On 2016-07-31, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> $ sage -q
What das sage -q do?
> sage: import cohomology # warning but fine!!
>
I haven't gotten a warning but a plain import error.
> In order to make it work, you can change *all* occurrences of
>
> include "
On 2016-07-31 01:09, Simon King wrote:
When trying to build the old-style version of my modular group
cohomology spkg, I now get:
pGroupCohomology/resolution.c:279:28: fatal error: struct_signals.h: No
such file or directory
#include "struct_signals.h"
The problem is this line in setup.py:
f
Francois Bissey wrote:
>
>> On 31/07/2016, at 18:54, leif wrote:
>>
>> This is what I get with GMP 6.1.1 (Sage 7.3.rc0, GCC 5.4.0):
>>
>> --
>> sage -t --long --warn-long 68.2 src/sage/structure/sage_object.pyx #
>> Killed due t
Presumably thats https://trac.sagemath.org/ticket/15585
On Sunday, July 31, 2016 at 9:57:46 AM UTC+2, François wrote:
>
> What’s the failure with simplicial_complex.py?
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
> On 31/07/2016, at 18:54, leif wrote:
>
> This is what I get with GMP 6.1.1 (Sage 7.3.rc0, GCC 5.4.0):
>
> --
> sage -t --long --warn-long 68.2 src/sage/structure/sage_object.pyx #
> Killed due to abort
> sage -t --long --war
leif wrote:
> Francois Bissey wrote:
>> The failing doctests are
>> sage -t --long
>> /usr/lib64/python2.7/site-packages/sage/rings/integer.pyx # 1 doctest
>> failed
>> sage -t --long /usr/lib64/python2.7/site-packages/sage/ext/memory.pyx
>> # 1 doctest failed
>> gmp and mpir report errors differ
14 matches
Mail list logo
