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
Update encoding lookup docs wrt #27938 #72579
Comments
The attached patch brings codecs docs up to date with respect to changes in bpo-27938. |
Thanks for the patch! Do we still need to keep the last sentence? Is there any other alternatives that can be used? Perhaps the word "spellings" can be changed with "aliases" to make the sentence a little bit clearer. |
I believe (but haven't checked) that additionally, encoding names are case insensitive with respect to the fast-path behavior. But then again I also suppose that's the way it was before bpo-27938 as well, which is why I didn't change that in this patch. But why not add it while at it, if I'm correct. Something like this revised patch? |
The names are indeed case-insensitive. However, something important is missing: the implementation details changed between Python 3.5 and 3.6. Please check the implementation for details and update the documentation with versionadded flags. Thanks. |
codecs-doc-3 contains a versionadded note about us-ascii. I think that's the only end user visible change in the new implementation. |
Thanks, Ville. |
I'm getting a 500 internatl server error trying to update https://bugs.python.org/review/28393/, so noting here that the latest review issue has been addressed in #4871 |
Thank you Ville Skyttä for your contribution! I merged your PR and backported it to Python 3.6. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: