-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-39337: Add a test case for normalizing of codec names #19069
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
e9ecac0
add a test case to against nomralizeing() of codecs
shihai1991 cf46290
remove redundant operation
shihai1991 59911e1
not clear all codec_search_paths
shihai1991 aa3c4d0
remove codecs_unregister()
shihai1991 aa4bf51
remove useless head file
shihai1991 8ce5956
remove useless import
shihai1991 41a1672
retrigger checks
shihai1991 00b300c
Merge remote-tracking branch 'origin/master' into bpo_1635741_1
shihai1991 f48e5d9
add codecs_unregister() in testinternalcapi
shihai1991 3795420
update code
shihai1991 e3b9365
Merge remote-tracking branch 'origin/master' into bpo_1635741_1
shihai1991 a2887f3
Using codecs.unregister() in test case
shihai1991 632a448
apply Tal's comment
shihai1991 bb6e78c
apply victor's comment
shihai1991 72e2435
apply tal's comment
shihai1991 26fcbe4
apply victor's comment
shihai1991 37b80e0
apply victor's comment
shihai1991 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
apply Tal's comment
- Loading branch information
commit 632a4480f506cd757981d1263e498f8b51d1de73
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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 :)