I've spent much of the last week arguing with nose, Jason Pellerin's unit testing framework for Python.
The fruits of that labor?
First, an extended introductory article and associated demo code, introducing, demonstrating, and discussing many nose features. (It's still a bit of a rough draft, folk. Send comments.)
Second, the pinocchio project. Yep, nose extensions. (Aren't I cute?) This adds 'stopwatch' and 'decorator' extensions to nose.
Putting wsgiref in the stdlib
Ever wonder how untested modules with non-standard interfaces and little documentation get into the stdlib?
Wonder no more.
No response from PJE.
Today I noticed that the bug I pointed out had been fixed. Neither of the e-mails were answered.
I posted publicly, I sent a private e-mail. What more should I do? I only got irritated when I saw the checkin fixing the bug without any acknowledgement of the other issues raised. <snark>Well, I guess once you've got Guido's OK, you don't need to listen to anyone else, right?</snark>
I'd be less irritated if the barrier to fixing problems once modules are in the stdlib wasn't so high. wsgiref will become effectively immutable -- overcomplicated constructor and all -- once it's integrated. That's presumably why GvR asked for comments, yeh?
Oh, well. Phillip -- if you actually want any contributions from me for wsgiref, you're going to need to answer my questions. I don't fancy writing documentation for an interface that could change, and I won't exactly enjoy bug testing your code in the future if I'm going to get the silent treatment for having the temerity to ask questions. (I'm not bucking for an apology here -- there's nothing to apologize for. Just be a member of the community, please.)
A bunch o' miscellaneous links
No new comments on scotch, but I did locate and write down
a bunch of other python-relevant HTTP recorders & proxies. Pound is particularly interesting.
apenwarr has an interesting parable on testing.
Busking and educating the police about the law. Priceless.
Domain Specific languages rock. Even in Ruby ;) ;).
autotest. Apart from the amusing quote about "not needing to open a Web browser to test" -- well, first of all, neither do I, and second of all, how much do you want to bet your site doesn't actually work the way you think it does? -- this autotest phenom sounds interesting. (py.test supports similar behavior.) Might be time to hack it into nose...
First on the list of things I didn't think would ever work -- crowdsourcing R&D!? Way cool.