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
Input and Output tutorial erroneously references default encoding UTF-8 #68917
Comments
In Doc/tutorial/inputoutput.rst, the docs state this about opening a file: Normally, files are opened in :dfn:`text mode`, that means, you read and write That statement is directly contradicted by the docs for open (Doc/library/functions.rst) which indicate: In text mode, if encoding is not specified the encoding used is platform The implementation matches the latter indication. |
corrected |
Hmm. It's a tutorial. It would probably be better to just say "the default is platform dependent" with a link to the open docs. |
@r.david.murray: just like that? (see patch v2) |
A direct link to open would be better ("see :func:`~functions.open`" should do it, I think). |
tried again :) |
Looks good to me assuming it renders correctly. |
@acucci and R. David Murray: I've run the patch locally, and all renders well except for one link. @acucci: I believe that the direct link to the ... "see :func:`open` " An example exists at the beginning of the section containing this line. The command in the current patch renders as plain text and not a link. If you can fix this small issue, the patch should be ready to merge (pending R David Murray's agreement). Thanks! |
ok, this time I tested the render myself and seems ok. For rendering I used sphinx. Sorry if I didn't try the final result in the first time, but I've never had the chance to use rst files before. |
New changeset c9e78d91d588 by Alessandro Cucci in branch '3.4': New changeset 20084be60761 by Jason R. Coombs in branch '3.4': New changeset 575e60ed7cb8 by Jason R. Coombs in branch '3.5': New changeset 47330144debd by Jason R. Coombs in branch 'default': |
Thanks for working through this Alessandro. I've applied your v3 patch and added a subsequent commit 20084be60761 to correct the open reference. |
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: