-
-
Notifications
You must be signed in to change notification settings - Fork 33.6k
gh-55531: Implement normalize_encoding in C
#136643
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
gh-55531: Implement normalize_encoding in C
#136643
Conversation
picnixz
left a comment
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.
I know that it's a draft but here are already some comments that you can dismiss if you're working on them.
|
I have cleaned up the changes and ensure the behavior remains the same, however there are still a few points I need input from @malemburg
|
ZeroIntensity
left a comment
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.
Would you mind running some microbenchmarks?
|
Benchmarks: scriptMain branch: This PR: |
|
Sorry for the lack of response. I'm currently at EuroPython and pretty busy with other things. I'll have a look on Saturday during the sprints. |
|
There are some subtle differences between Python and C code. We first need to decide what normalization is needed in Python and C code. It seems that excessive normalization caused problems (see #88886). |
All of our tests pass, and from my further testing it also matches behaviour, can you please point out such cases? These are long standing issues that have had no progress for quite a while, I propose, to keep this PR simple/organized and therefore focused on switching the implementation to the existing C code. This PR will become more complex and therefore harder to review if it has to rewrite the existing C code too. The existing issues, and yours from a few days ago, can be addressed in the C implementation, rather than both implementations. |
|
I suggest holding this PR until we solve other issues. Otherwise it will make backporting other changes more difficult. I have some comments about this PR, but it's too early to address them because in the end, everything could change radically. |
|
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 |
|
Thanks for making the requested changes! @malemburg: please review the changes made to this pull request. |
|
Friendly ping @malemburg |
|
I think we first need to have #137167 merged and then this one. |
malemburg
left a comment
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.
LGTM. Please remove the unneeded forward def in codecs.c.
|
@malemburg Is there anything left to do here? |
|
Thanks, @StanFromIreland, for working on this. I don't think this can be backported, since it's a new feature in a way. |
|
I agree. |
Uh oh!
There was an error while loading. Please reload this page.