-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
bpo-24925: _find_lineno now finds doctest __test__ string line numbers #17553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
If the doctest code is in a test string, _find_lineno now find the error, by looking for a line in the docstring that is unique in the source file.
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
I hope bedevere-bot likes me now.
News file for patch 17553, issue 24925
|
I am having a bit of trouble getting my news file to work here. |
Issue 24925 has a patch for finding line numbers in __test__ docstrings. This code actually tests that.
This file is used by test_doctest.
Made it a bit more clear for posterity: now tells that you shouldn't edit the 'q' test.
|
Yes, it is now actually tested and it works! |
Just after I claimed it was fixed, I made a typo. Anyway.
If the doctest code is in a test string, _find_lineno now find the error, by looking for a line in the docstring that is unique in the source file.
https://bugs.python.org/issue24925