| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
The new test case is good, and the implementation changes are headed in the right general direction. However, it should be sufficient to reorder the existing operations, rather than calling _PyUnicode_XStrip twice.
Sorry, something went wrong.
| Py_ssize_t text_len = PyUnicode_GET_LENGTH(self->text); | ||
| PyObject *data = PyUnicode_Substring(self->text, PRINT_OFFSET, text_len); | ||
| // Issue 32028: Handle case when whitespace is used with print call | ||
| PyObject *initial_data = _PyUnicode_XStrip(self->text, 2, strip_sep_obj); |
There was a problem hiding this comment.
Rather than adding a new call to _PyUnicode_XStrip, just reorder the existing operations:
Sorry, something went wrong.
There was a problem hiding this comment.
A minor point I missed when reviewing the original PR: defining and using const int STRIP_BOTH = 2; will make the _PyUnicode_XStrip call more self explanatory.
So we may as well make that change now, since the code is being modified anyway.
Sorry, something went wrong.
There was a problem hiding this comment.
+1 for the const int STRIP_BOTH = 2;. I was explaining my patch to a few folks and I had to consult my blog for that particular thing. Few months down the line I didn't even remember that.
So, yes that would be great.
Sorry, something went wrong.
There was a problem hiding this comment.
@ncoghlan So, while I modified the code, one of the test cases fails with re-ordering the code. That test case is:
test_string_with_excessive_whitespace. Since we're only stripping the the data at the beginning, and then directly trying to extract the sub-string.
I think we may need to strip the leading chars to make the previous test case pass. What do you say?
Sorry, something went wrong.
There was a problem hiding this comment.
I've pushed my current code which re-orders the existing operations & the test_string_with_excessive_whitespace is failing. I'm waiting for your reply on this. I think we might want to strip the leading whitespace from data.
Sorry, something went wrong.
|
|
||
| def test_string_with_leading_whitespace(self): | ||
| python2_print_str = '''if 1: | ||
| print "Hello World" |
There was a problem hiding this comment.
Since we're stripping all leading whitespace, you may as well indent this 4 spaces relative to the target variable name (so 12 leading spaces total)
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
There was a problem hiding this comment.
Don't forget to check for errors and count references.
Sorry, something went wrong.
| const int STRIP_BOTH = 2; | ||
| // Issue 32028: Handle case when whitespace is used with print call | ||
| PyObject *initial_data = _PyUnicode_XStrip(self->text, STRIP_BOTH, strip_sep_obj); | ||
| Py_ssize_t text_len = PyUnicode_GET_LENGTH(initial_data); |
There was a problem hiding this comment.
initial_data can be NULL.
Sorry, something went wrong.
| PyObject *initial_data = _PyUnicode_XStrip(self->text, STRIP_BOTH, strip_sep_obj); | ||
| Py_ssize_t text_len = PyUnicode_GET_LENGTH(initial_data); | ||
| PyObject *data = _PyUnicode_XStrip( \ | ||
| PyUnicode_Substring(initial_data, PRINT_OFFSET, text_len), \ |
There was a problem hiding this comment.
The result of PyUnicode_Substring() can be NULL.
Otherwise it will be leaked.
Sorry, something went wrong.
|
@serhiy-storchaka Nice catch! Sorry, I missed those memory leaks. I've tried to address those issues. Can you please take a pass. |
Sorry, something went wrong.
There was a problem hiding this comment.
Please remove redundant empty lines.
Sorry, something went wrong.
There was a problem hiding this comment.
I'd missed that the second _PyUnicode_XStrip call handled excess whitespace between print and the expression being printed, so I was wrong about that being redundant (and the regression test suite was right).
I've adjusted the NEWS entry wording, so +1 from me (I'll merge once CI finishes).
Sorry, something went wrong.
|
Thank you so much @ncoghlan & @serhiy-storchaka :) |
Sorry, something went wrong.
|
@serhiy-storchaka @ncoghlan I guess we can merge this now :) Also needs a backport to 3.6 label on this one. |
Sorry, something went wrong.
|
Hi @serhiy-storchaka @ncoghlan Do we need something else here? Please let me know and I'll do that :) |
Sorry, something went wrong.
|
Just closing & reopending to restart the CI (Appveyor's a required check now, and it didn't run properly) |
Sorry, something went wrong.
|
Thanks @CuriousLearner for the PR, and @ncoghlan for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Sorry, something went wrong.
The suggested replacement for print statements previously failed to account for leading whitespace and hence could end up including unwanted text in the proposed call to the print builtin. Patch by Sanyam Khurana. (cherry picked from commit d57f26c)
|
GH-5249 is a backport of this pull request to the 3.6 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This fixes the newly added print suggestion for cases when there is leading whitespace in the initial data.
I've also added a test case for this. @ncoghlan Can you please check this?
https://bugs.python.org/issue32028