Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #25430
| From | Peter Otten <__peter__@web.de> |
|---|---|
| Subject | Re: assertraises behaviour |
| Date | 2012-07-16 19:27 +0200 |
| Organization | None |
| References | <CAF_E5JYANst57yOud+Ot0AbKkePruoCGPUNC5BbyBoMbgaw2_Q@mail.gmail.com> <ju16g6$8o2$1@dough.gmane.org> <CAF_E5JZNrusmb2SziNBOah67ioZG0yf_w5RNJxVVrU8B5Tqzuw@mail.gmail.com> <ju1att$hc4$1@dough.gmane.org> <CAF_E5Ja4kzHGa9vEr5CML5wV7ampCULRRGt=9JtRoqn4Xxummw@mail.gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.2182.1342459676.4697.python-list@python.org> (permalink) |
andrea crotti wrote: > Good thanks, but there is something that implements this behaviour.. > For example nose runs all the tests, and if there are failures it goes > on and shows the failed tests only in the end, so I think it is > possible to achieve somehow, is that correct? No, I don't see how the code you gave above can fail with an OSError. Can you give an example that produces the desired behaviour with nose? Maybe we can help you translate it to basic unittest.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: assertraises behaviour Peter Otten <__peter__@web.de> - 2012-07-16 19:27 +0200
csiph-web