Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make PipTestEnvironment stderr checks more assertive
See original GitHub issueWe can tighten the tests in the following way. Rename the PipTestEnvironment.run() arguments of allow_stderr_warning and allow_stderr_error arguments to expect_stderr_warning and expect_stderr_error:
and make the test fail if the argument is passed and a warning or error isn’t present, respectively. The idea is that the argument should only be passed if it’s actually needed, unlike the current case where the test is passing if the argument is provided unnecessarily.
Also, to do this it might be necessary to do a check of some kind to know if the argument should be passed. For example, whether a deprecation warning is emitted can depend on what version is running.
Posted in its original form by @cjerdonek in #161 (comment)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey @ssurbhi560. Thanks for pinging me! Can’t really find a time to get this done. Would you like to pick it up? Please, feel free to 🙏
Hey @gutsytechster! I won’t be able to work on this right now, feel free to work on it. 😃