No subject

Mon Jan 15 22:11:34 PST 2007

-> py.test and nose might be great, but the only way I'd know about them
-> is if I went searching for them, something most people won't do unless
-> they hit some serious problem in their day-to-day encounters with
-> unittest.

This is true.  So, perhaps we should propose that either nose or py.test
get dropped into Py3K, instead of a new unittest module?  Obviously I'd
personally like nose, but I'd prefer py.test+unittest runner over
yet another unittest framework.


More information about the testing-in-python mailing list