I've been ignoring the fact that WebOb has very light test coverage for a while now, but I've just run into a bug that makes it clear that my blissful head-in-the-sand days are nearing an end.
Is anyone interested in leading a task to give WebOb 100% test coverage? It's a fairly large task, inglorious, and boring, but straightforward and will help *lots* of people inside and outside the Pylons community. If so, please respond here. - C -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-de...@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.