I opened an issue: https://github.com/pytest-dev/pytest/issues/889
Omar On Sat, Jul 25, 2015 at 6:22 PM, Florian Bruhin <[email protected]> wrote: > * Omar Kohl <[email protected]> [2015-07-25 15:26:09 +0200]: > > Any suggestion on what can be done to fix this? Can/should I open an > issue? > > > > In a way it could be seen as a PyCharm problem, but I can see why they > > would want to prevent output capturing to be able to do this themselves > in > > their console. On the other hand it also happens when running the test on > > the console having disabled capturing (-s). > > > > Is it possible/reasonable to fail or skip the test if it is detected that > > output is not being captured? (Remember currently it just freezes, which > I > > think is very confusing!). > > Please open an issue - I agree at the very least the tests should be > skipped when the output isn't captured. > > Florian > > -- > http://www.the-compiler.org | [email protected] (Mail/XMPP) > GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc > I love long mails! | http://email.is-not-s.ms/ > > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev > >
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
