-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-136162: Document encodings
#136164
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
base: main
Are you sure you want to change the base?
gh-136162: Document encodings
#136164
Conversation
@StanFromIreland please, coordinate your work with others :) |
@sobolevn Oops... I must have missed it in your post. I believed that no one else had started work on it so I went ahead. I didn't see value in saying I was working on it if I am to open PR ten minutes later. Apologies! |
We can reopen it, since yours was the first one :) |
Looks good, but you should also document the win32_code_page_search_function() function available on Windows for completeness. |
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, thanks @StanFromIreland
@malemburg thanks for the well commented code, which is the basis for my doc:-) |
search_function
has possibly the longest singleif
statement in the entirety of CPython...I added a
.. note::
, but switching to a.. warning::
seems like a good idea.I am split on documenting
win32_code_page_search_function
, but I have a patch ready. To me it seems as more of a helper function, which could be made private.encodings
module is not documented #136162📚 Documentation preview 📚: https://cpython-previews--136164.org.readthedocs.build/en/136164/library/codecs.html#module-encodings