Help with nose 1.x and 2.x...

[John Szakmeister]

Hi Jason,

I know you're a bit strapped for time, and was wondering if there was
anything I could do to help with either one. I've been a long-time
user of nose, and been programming Python for 10+ years now. I don't
have a lot of time either, but I'm willing to spend some of it on
nose, since it's a tool I reach for often.

Let me know if there's any way I can help!

-John

[jason pellerin]

Hi!

Thanks and sorry for taking so long to write back. I definitely will take any help you have to give. :) Sadly what nose *really* needs is a new primary maintainer, since neither I nor Kumar really have the time anymore to handle it. But that's sort of a giant step.

So, any time at all that you have to read and comment on pull requests would be very helpful -- it often takes me a week or more just to look at a new one, and even good ones tend to linger for a long time before getting merged.

Or if you want to try to fix that one pesky timing test that sometimes fails on travisci, that would be really helpful because we'd be able to trust the tests again.

For nose2, the thing needed most right now is more users, so if you haven't tried it out on a real project, try it out!

Thanks again,

JP

-John

--
You received this message because you are subscribed to the Google Groups "nose-dev" group.
To post to this group, send email to nose...@googlegroups.com.
To unsubscribe from this group, send email to nose-dev+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nose-dev?hl=en.

[John Szakmeister]

On Sun, Nov 11, 2012 at 8:45 AM, jason pellerin <jpel...@gmail.com> wrote:
> Hi!
>
> Thanks and sorry for taking so long to write back. I definitely will take
> any help you have to give. :) Sadly what nose *really* needs is a new
> primary maintainer, since neither I nor Kumar really have the time anymore
> to handle it. But that's sort of a giant step.

No worries Jason! I know we're all pressed for time.

I don't know if I'm ready to be the primary maintainer just yet, but
I've certainly gotten to know the internals. We're building a system
test tool for a system used to position antennas, and have gotten to
re-experience some of nose's strengths, and some of its weaknesses as
well.

> So, any time at all that you have to read and comment on pull requests would
> be very helpful -- it often takes me a week or more just to look at a new
> one, and even good ones tend to linger for a long time before getting
> merged.

Sure thing. Is there some way I can mark ones that I think are ready
for merge? Would you like me to stage them somewhere?

> Or if you want to try to fix that one pesky timing test that sometimes fails
> on travisci, that would be really helpful because we'd be able to trust the
> tests again.

I'll take a stab at it. I pushed up one potential fix. I think I'm
going to have to install PyPy to find the other.

> For nose2, the thing needed most right now is more users, so if you haven't
> tried it out on a real project, try it out!

I'll take a look when I get a chance!

-John