[Cython] 0.16 release

Robert Bradshaw robertwb at math.washington.edu
Sun Feb 5 11:31:58 CET 2012


On Sat, Feb 4, 2012 at 10:49 AM, Vitja Makarov <vitja.makarov at gmail.com> wrote:
> 2012/1/31 Robert Bradshaw <robertwb at math.washington.edu>:
>> On Sat, Jan 28, 2012 at 8:05 AM, Vitja Makarov <vitja.makarov at gmail.com> wrote:
>>> 2012/1/26 Jason Grout <jason-sage at creativetrax.com>:
>>>> On 1/25/12 11:39 AM, Robert Bradshaw wrote:
>>>>>
>>>>> install
>>>>>
>>>>> https://sage.math.washington.edu:8091/hudson/view/ext-libs/job/sage-build/lastSuccessfulBuild/artifact/cython-devel.spkg
>>>>> by downloading it and running "sage -i cython-devel.spkg"
>>>>
>>>>
>>>>
>>>> In fact, you could just do
>>>>
>>>> sage -i
>>>> https://sage.math.washington.edu:8091/hudson/view/ext-libs/job/sage-build/lastSuccessfulBuild/artifact/cython-devel.spkg
>>>>
>>>> and Sage will (at least, should) download it for you, so that's even one
>>>> less step!
>>>>
>>>> Jason
>>>>
>>>
>>> Thanks for detailed instruction! I've successfully built it.
>>>
>>> "sage -t -gdb ./...." doesn't work, is that a bug?
>>>
>>> vitja at mchome:~/Downloads/sage-4.8$ ./sage  -t -gdb
>>> devel/sage/sage/combinat/sf/macdonald.py
>>> sage -t -gdb "devel/sage/sage/combinat/sf/macdonald.py"
>>> ********************************************************************************
>>> Type r at the (gdb) prompt to run the doctests.
>>> Type bt if there is a crash to see a traceback.
>>> ********************************************************************************
>>> gdb --args python /home/vitja/.sage//tmp/macdonald_6182.py
>>> starting cmd gdb --args python /home/vitja/.sage//tmp/macdonald_6182.py
>>> ImportError: No module named site
>>>         [0.2 s]
>>>
>>> ----------------------------------------------------------------------
>>> The following tests failed:
>>>
>>>
>>>        sage -t -gdb "devel/sage/sage/combinat/sf/macdonald.py"release
>>> Total time for all tests: 0.2 seconds
>>
>> Yes, that's a bug.
>>
>>> I've found another way to run tests (using sage -sh and then direct
>>> python ~/.sage/tmp/...py)
>>>
>>> So I found one of the problems. Here is minimal cython example:
>>>
>>> def foo(values):
>>>    return (0,)*len(values)
>>> foo([1,2,3])
>>>
>>> len(values) somehow is passed as an integer to PyObject_Multiply()
>>
>> Yeah, that's a bug too :).
>
> I've fixed tuple mult_factor bug here:
>
> https://github.com/cython/cython/commit/2d4b85dbcef885fbdaf6a3b2daef7a017184a56f
>
> No more segfaults in sage-tests but still 7 errors.
>

Thanks! I've looked into the other errors and I think it boils down to
our use of --disable-function-redefinition being incompatible with how
decorators work. Of course that was just a hack, so I've fixed sage to
build/startup without using that flag, but there's some strangeness
with import order now that I haven't had time to resolve yet.


More information about the cython-devel mailing list