Skip to content

gh-93600: Clarify the meaning of buffering=-1 in open() #93685

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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

eamanu
Copy link
Contributor

@eamanu eamanu commented Jun 10, 2022

This commit clarify the meaning of buffering=-1 in open() function. Add
this information in Docs and in source code docstring.

This commit clarify the meaning of buffering=-1 in open() function. Add
this information in Docs and in source code docstring.
@AA-Turner
Copy link
Member

I think you need to regenerate the frozen version of _io -- make regen-all. That should hopefully fix CI.

A

Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar, and a minor change from "default buffer size" to "default buffering policy" -- this ties in the following text and helps communicate that -1 is the same as passing no argument.

A

eamanu and others added 7 commits June 10, 2022 20:06
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
@eamanu
Copy link
Contributor Author

eamanu commented Jun 10, 2022

HI @AA-Turner thanks for the revision. I've just push some changes, I applied the your recommendations and I pushed a commit running clinic.py, I hope that fix the build :-)

Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, it did fix the build -- you need to re-wrap two lines though and then go through the regen dance again!

A

Copy link
Member

@merwok merwok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest changes to minimize diff churn.
Lines shorter than the limit are no problem, and this keeps git history slightly more useful 🙂

eamanu and others added 3 commits August 9, 2022 07:19
Apply suggestion of @merwok

Co-authored-by: Éric <merwok@netwok.org>
Apply suggestion of @merwok

Co-authored-by: Éric <merwok@netwok.org>
Apply suggestion of @merwok

Co-authored-by: Éric <merwok@netwok.org>
@eamanu
Copy link
Contributor Author

eamanu commented Aug 9, 2022

Ready thanks @merwok

@hugovk hugovk removed the needs backport to 3.10 only security fixes label Apr 7, 2023
@erlend-aasland erlend-aasland self-assigned this Jan 12, 2024
@hugovk hugovk added needs backport to 3.12 only security fixes and removed 3.12 only security fixes needs backport to 3.11 only security fixes labels Apr 11, 2024
@serhiy-storchaka serhiy-storchaka added the needs backport to 3.13 bugs and security fixes label May 9, 2024
@willingc
Copy link
Contributor

Thanks @eamanu. It looks like the merge conflicts need to be resolved. Please ping me once they are updated. Thanks.

@hugovk hugovk removed the needs backport to 3.12 only security fixes label Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting changes docs Documentation in the Doc dir needs backport to 3.13 bugs and security fixes skip news topic-IO
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

8 participants