-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-43049: Use io.IncrementalNewlineDecoder for doctest newline conversion #24359
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
No new test is needed because existing tests already cover this code, is that correct? |
Yes, that's correct. |
This PR is stale because it has been open for 30 days with no activity. |
Just saw the stale notification, bumping to get an update on merging this PR. |
I was leaving this for anyone more familiar with either |
|
I'm going to declare that buildbot failure Not Our Fault™ :). I also got an email about a Ubuntu check failure, which also appears unrelated to this change. |
This PR is a follow-up to PR #17385 for bpo-1812 (now merged). During discussion on that issue the suggestion was made to investigate whether any resources already provided by the io module might be available to do the newline conversion in doctest that was corrected in that PR. It turns out there is: the io.IncrementalNewlineDecoder object does exactly the conversion that is needed. This PR implements using that object in place of the custom newline conversion that was done in the previous PR. The only change is in the relevant code in the doctest module.
https://bugs.python.org/issue43049