We need help working on code coverage for Cython code

[Juan Nunez-Iglesias]

A honking good idea!

... But I am very much flat out for the next 2-3 months, so I will have to
watch from the sidelines...

Thank you!

Juan.


On Fri, Aug 8, 2014 at 11:55 AM, Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> Over on another mailing list, we've hit a big problem trying to work
> out coverage on a large amount of Cython code.
>
> As y'all probably know, there's no automated way of checking code
> coverage on Cython code at the moment.
>
> The Cython developers have done some work on this [1] but it is
> currently stalled for lack of developer time to work on it.
>
> We'd really like to get this working, and the Cython developers have
> offered to help, to get this started.
>
> Can anyone help us out by a) joining an interactive discussion for 15
> minutes or so with the Cython developers to get us started b) helping
> with a short burst of coding that will follow, we estimate a few days.
>
> I think this is something many of us need, and it would also be a
> thank you to the Cython team for their work, which we all use so much.
>
> Cheers,
>
> Matthew
>
> [1] http://trac.cython.org/cython_trac/ticket/815
>
> --
> You received this message because you are subscribed to the Google Groups
> "scikit-image" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to scikit-image+unsubscribe at googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scikit-image/attachments/20140808/92f3124a/attachment.html>