Message283970
I don't believe this is coverage.py's fault, so I don't have an answer to your question. There is no revision of coverage.py that *does* swallow stderr. Also, as you can see from the test output, it isn't swallowed, it's not being captured where it should be captured, but it is appearing on the terminal. I see more than 60 uses of captured_stderr in the Python test suite. If coverage.py were swallowing stderr, I would expect dozens of test failures. The problem is more subtle.
If you want, you can bisect against any revision of coverage.py you like, perhaps the released 4.2? |
|
Date |
User |
Action |
Args |
2016-12-24 19:26:47 | nedbat | set | recipients:
+ nedbat, r.david.murray, serhiy.storchaka, patriki |
2016-12-24 19:26:47 | nedbat | set | messageid: <1482607607.87.0.402992891785.issue29048@psf.upfronthosting.co.za> |
2016-12-24 19:26:47 | nedbat | link | issue29048 messages |
2016-12-24 19:26:47 | nedbat | create | |
|