[Cython] 0.16 release
robertwb at math.washington.edu
Wed Jan 25 18:39:17 CET 2012
On Wed, Jan 25, 2012 at 4:17 AM, mark florisson
<markflorisson88 at gmail.com> wrote:
> On 25 January 2012 12:00, Stefan Behnel <stefan_ml at behnel.de> wrote:
>> mark florisson, 25.01.2012 11:43:
>>> On 25 January 2012 01:27, Robert Bradshaw wrote:
>>>> On Mon, Jan 23, 2012 at 2:27 AM, mark florisson wrote:
>>>>> It's been almost three months since we talked about a 0.16 release, I
>>>>> think it's quite ready. It would already be a big release, it would be
>>>>> good to see how people like it, and to catch any issues etc before we
>>>>> pile on more features.
>>>> I would love to do a release soon. Last time this came up, I think the
>>>> big issue was (compilation) performance regression. Has this been
>>>> adequately addressed?
>>> Sort of. Basically if you don't use memoryviews it will be as fast as
>>> it used to be, otherwise there is about a 3 second constant time
>>> overhead (on my machine).
>>>> The other issue is that there are a couple of
>>>> doctest failures with Sage. One source of problems is decorators due
>>>> to the (ugly) disallowing of function re-declarations, I'll try look
>>>> into this one. There are also a huge number of segfaults (see the
>>>> bottom of https://sage.math.washington.edu:8091/hudson/view/ext-libs/job/sage-tests/lastSuccessfulBuild/artifact/log.txt
>>>> ) which we need to get to the bottom of.
>>> Oh I see. I suppose to try it out under a debugger one would have to
>>> compile the whole of sage from source?
>> It might be easier to log into sage.math, go to the sage build directory
>> that Jenkins uses and do some experiments there. It's in
And compiling Sage from scratch isn't actually that hard: type "make"
and wait a couple of hours. I've updated the description at
to explain how to build a cython-devel sage locally as others have
asked for this as well, in summary you apply the patch at
to the repo in $SAGE_ROOT/devel/sage-main/ , install
by downloading it and running "sage -i cython-devel.spkg" and then do
"sage -ba" to re-build all Cython files.
sage -gdb and sage -t -gdb /path/to/file are useful to know as well.
More information about the cython-devel