GeezerVison

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your 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 your contribution, we look forward to reviewing it!

I've signed the CLA with both my github name and BPO name.

Thanks for the PR. This would require signing a CLA as indicated. Travis fails due to indentation in your code. Please run make patchcheck to fix the whitespace errors. This would also require tests for the new code with single and multi line comments along with a NEWS entry. I would wait for inputs from others on the tracker or PR to proceed further on how this can be approached.

You can use strncmp() rather than PyOS_strnicmp(), no need case-insensitive comparison here.
-- left by a passerby

Using strcmp() is wrong, strncmp() is suitable.

You also need add test-cases, I guess you can modify existing test-case with some comments.

And a "News Entry", using blurb to create is very easy, see https://devguide.python.org/committing/#what-s-new-and-news-entries

strcmp(p, "*/") will always return non-zero value, unless "*/" appears at the end of a string, because strcmp() doing comparision until the implied ending '\0'.

To be honest, I'm not very skilled too.

From my reading of strcmp(p, "*/") it depends on the shorter of the strings, so because it is in a loop per char, it will still terminate early, successfully. I have moved to strncmp though to avoid any ambiguity in the code for future reference.

@montanalow you have signed the CLA but your github is not associated to your BPO account. Could you update it because without that we can not review your code. Thank you

Thanks for the PR, but closing as the CLA has not been signed within the last month. If you do decide to sign the CLA we can re-open this PR.

See also #13216 which solves this much more reliably.