[TIP] State of nose?

Hi,
Good questions! In general, with 2 small children at home and a
much-reduced ability to work on oss projects during business hours, I
don't have time to do much beyond cheerlead for nose and (in theory)
coordinate patches and releases for nose2.
Kumar McMillan is holding the pumpkin for the 1.1 release of nose,
which is expected to be done as soon as we can work out some
multiprocessing and build-related bugs.
Beyond that, my plan has been to move on to a BSD-licensed nose2
package based on the unittest2 plugins branch. You can see the work
that I've done on that so far here:
https://bitbucket.org/jpellerin/nose2/overview
But the plugins branch of unittest2 (at least where I have been
pulling from, http://hg.python.org/unittest2/) hasn't been updated in
a while and I don't know what the state or plans are for that, so I'm
not sure exactly what's going to happen with nose2. Last I recall,
Michael was working on a major refactoring of how hooks work, and I've
been waiting for that to land to do any more work on nose2.
JP
On Mon, Jul 18, 2011 at 6:40 PM, Victoria G. Laidler <laidler at stsci.edu> wrote:
> Hi gang,
>> What's the current status/plans for nose? I seem to remember discussions
> from Pycon 2010 that Jason(?) didn't feel he had time to continue support,
> and then there were some discussions for a successor package supported by
> the community.... so where do we stand with all that?
>> thanks,
> Vicki Laidler
>>> _______________________________________________
> testing-in-python mailing list
>testing-in-python at lists.idyll.org>http://lists.idyll.org/listinfo/testing-in-python>