On Oct 23, 2009, at 2:10 AM, Stefan Behnel wrote:

> Robert Bradshaw wrote:
>> As mentioned earlier, it's about time to release Cython 0.12.
>
> Totally.
>
>> What I see that needs to happen is
>>
>> 1) Get Sage working with the new Cython. I've gotten Sage to compile
>> and nearly all doctests passing
>
> You can switch the cascaded assignment work-around back to the  
> original
> code, I fixed #409.

Thanks.

>> I think I'm down to one bug,
>> somewhere in exception handling, but I haven't been able to look at  
>> it
>> much yet
>
> Any more hints on this? I might be able to help out.

Sure. I get
SystemError: NULL result without error in PyObject_Call
I haven't tried to pull it out into an isolated failure yet. 
http://trac.sagemath.org/sage_trac/ticket/7272 
  the file in question is
http://hg.sagemath.org/sage-main/file/5bf36a37cd0c/sage/modular/modsym/heilbronn.pyx#l400
>> I'd assume lxml and other developer projects are building
>> with the current head.
>
> lxml tests fine, but it's certainly worth removing some C-isms from  
> its
> code once I start depending Cython 0.12. If all those new  
> optimisations had
> been in Cython two years ago, the code would look a lot cleaner today.

Same for Sage.

>> 2) We should go onto the trac server (link below) and either resolve/
>> bump any tickets that are not going happen in the next week or two.
>
> I'll see that I get the tickets closed that I'm still working on.  
> Most of
> the currently tickets do not look like the need fixing right now,  
> but we
> should at least get all tests working on the supported platforms.
>
>
>> 3) Widespread testing.
>
> Oh, yes, please! :)
>
> It seems from the reports we had on the list that many users have  
> already
> been running cython-devel recently. But it would be good to get some
> feedback especially from Windows/Mac users, as I expect most  
> developers to
> be on Linux nowadays.

I actually mostly use a Mac (10.5) but 10.4 and 10.6 testing, as well  
as Windows, would be good.

> Given the amount of changes, I'd also expect at least two release
> candidates, and I really hope that people will exercise them. It's
> definitely worth switching from 0.11. Remember: *before* a new major
> release is the best time to get your bugs fixed, not afterwards.

Agreed. And we should make sure to test things like --embed too  
(perhaps this should be part of runtests, introducing a make test  
target in the demo).

- Robert

_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to