Robert Bradshaw, 17.07.2010 18:23: > On Sat, Jul 17, 2010 at 3:46 AM, Stefan Behnel wrote: >> I'll take a look at the current cython-devel failures in Py<=2.5 as I broke >> at least one of them while fixing Unicode problems on narrow platforms, but >> I'd be happy to get some help in fixing the others. Some tests have been >> broken for ages. See e.g. the end of >> >> https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/cython-devel-tests-py24-c/138/console > > What's the ETA for this? I thought that once Sage built, that was the > last major problem.
I think it was. Most test failures looked like it was just the tests that were broken. I fixed most of them. Here's the last one that I'm not sure about. In any case, given that it's a pure pre-Py2.5 issue, it's nothing that would be worth delaying a release. https://sage.math.washington.edu:8091/hudson/view/cython-devel/job/cython-devel-tests-py24-c/148/testReport/doctest/DocTestCase/Doctest__ssize_t_T399/ > In any case, +1 to merging into -devel and making > that bugfix-only so we can actually release. +1 > Does anyone want to go to > http://trac.cython.org/cython_trac/milestone/0.13 and bump stuff to > 0.13.1 (or later) if it's not trivial or a blocker? (I'll do this if > no one beats me too it, but I've got to run now.) I'll take another look, and I think all core developers should do that. Adding a short comment when changing the target milestone or making something a blocker would be nice. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
