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 backward-compatibility magic optional
See original GitHub issueI had some trouble with getting my large test suite to work properly with pytest. A debugging session revealed that I was using method names that pytest identified as “unittest” names, and then also as “nosetest” names. Pytest treated the methods specially as a result. Better for me would be if that helpful magic could be disabled, so that I get just-plain pytest.
My suggestion is to have options --legacy=unittest and --legacy=nosetest, and have to opt-in to that behavior. This would be a breaking change, so making it opt-out instead of opt-in is also a reasonable path.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 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
most likely
Closing as opt-out is possible as described above, and will track deprecation in #6973.