Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

CLA Missing

Our records indicate the following people have not signed the CLA:

@enjoy-binbin

For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

If you have recently signed the CLA, please wait at least one business day
before our records are updated.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

Why did you close this? The CLA? For spelling corrections, we merely prefer the CLA, but don't need it, as the change is from a 'creative' misspelling to the dictionary standard. You cannot copyright the correct spelling. I will apply this, but hope you go ahead and sign it now so you are ready for a future PR.

The initial Pipelines failure? It is a build failure, which should be unrelated to the PR and should be transient.

@terryjreedy Hi. Thanks for your reply. I am new. That means a lot to me.
The only reason i closed it because the CLA... I have applied for the sign, juse wait the result
So that i can reopen again. Avoid disturbing you guys. But it seems that you have been mentioned

Thanks again for your time!

Reverting configure.ac did not work, so I made sure updated to latest main.

@terryjreedy - be careful with this one, I spotted some changes that weren't good.

@cjw296 Please be specific. A couple of hours ago I reviewed carefully and already reverted, corrected, or checked everything I though questionable.

@cjw296 I recheck and found this: in ssl.py, 'woth' should by 'with', not 'worth'. Fixed. I think others looks good in context.

Bin-bin, If you (or anyone else) are on Linux and can run 'make regen-all' and commet whatever that changes, please try that.

@terryjreedy It seems that re-gen was ok. I was trying to solve that one half hour ago.
But i only have a centos and i encounter some problems.
Now look like the hardest part has been solved.

Sorry for that, i didn't expect to cause this problem... and others minor fix
Thanks a lot, it must have cost you a lot of time

On corementorship, Guido said how to rebuild on windows: PCbuild\build -r. importlib_external.h was rebuilt, followed by errors that disappeared on rerun. I will redo the the misspellings I reverted and is that does not create a problem, merge.

Thanks @enjoy-binbin for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒⛏🤖

Sorry, @enjoy-binbin and @terryjreedy, I could not cleanly backport this to 3.10 due to a conflict.
Please backport using cherry_picker on command line.
cherry_picker 17b16e13bb444001534ed6fccb459084596c8bcf 3.10

Yes, more time than expected. At least I learned that rebuilding can be done on Windows. I have seen the make message before and assumed I had to have a make system. Another core def suggested that the error message should be more informative.

I expected that auto backport would fail even though most of these misspelling either originated with or were backported at least to 3.10. If you do a 3.10 backport that passes tests , I will review and merge. Using the cherry_picker module is easier than git cherry-picker as it automates more. Whether and how are up to you.