Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
bpo-39337: Add a test case for normalizing of codec names #19069
bpo-39337: Add a test case for normalizing of codec names #19069
Changes from 10 commits
e9ecac0
cf46290
59911e1
aa3c4d0
aa4bf51
8ce5956
41a1672
00b300c
f48e5d9
3795420
e3b9365
a2887f3
632a448
bb6e78c
72e2435
26fcbe4
37b80e0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fact that the codec names are normalized via the
normalizestring
function is an implementation detail, so the test should be written ignoring that detail, to the extent possible. This includes its documentation, so...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I considered this details before. Why I am still leave this detail?
IMHO, leave enough details can help developers to maintain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're welcome to add a comment after the doc-string. I wouldn't want the doc-string to mention normalizestring, though, unless we change the test to call
normalizestring()
directly instead ofcodecs.lookup()
, which I don't recommend.From my experience, however, such comments often become outdated when the implementation changes. And outdated comments causing confusion are usually worse than no comments.
Also, if someone needs to see the details, they'll likely need to go through the code starting at
codecs.lookup()
anyways. It's relatively straightforward to follow:codecs
importslookup
from_codecs
, implemented inModules/_codecsmodule.c
.lookup()
is a simple wrapper for_PyCodec_Lookup
fromPython/codecs.c
. With the imports and wrappers out of the way,_PyCodec_Lookup
callsnormalizestring()
near the top of the function, immediately after a bit of initialization.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your share, Tal. It's make sense :)