Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

gh-62734: Document that open()'s file param becomes name attribute#144455

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
kovan wants to merge2 commits intopython:main
base:main
Choose a base branch
Loading
fromkovan:gh-62734-open-name-attr

Conversation

@kovan
Copy link
Contributor

@kovankovan commentedFeb 3, 2026•
edited by github-actionsbot
Loading

Summary

  • Clarifies that the value passed as thefile parameter toopen() is stored in thename attribute of the returned file object

Test plan

  • make check passed
  • Documentation builds correctly

🤖 Generated withClaude Code

📚 Documentation preview 📚:https://cpython-previews--144455.org.readthedocs.build/

Clarify that the value passed as the *file* parameter to open() isstored in the name attribute of the returned file object.Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The name attribute is documented under io.FileIO, not io.IOBase.Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Copy link
Member

@ZeroIntensityZeroIntensity left a comment

Choose a reason for hiding this comment

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

Please take the history of the issue into account before opening a PR. It's not clear that this is the immediate change that we want to make.

More generally, please do not spam us with AI-generated pull requests. Despite what you might think, these are often not helpful contributions and waste maintainer time.

If you're interested in contributing to CPython, I really suggest finding an area that you're interested in, spending the time to thoroughly investigate and triage an issue, and then finally submitting a PR. Otherwise, if you continue to do this, we have no choice but to block you.

@bedevere-app
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phraseI have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@kovan
Copy link
ContributorAuthor

kovan commentedFeb 4, 2026•
edited
Loading

Block me? haha that's funny. I can just open another GitHub account, eliminate any trace of AI intervention in the commits and PRs and you will have to use your brain to know if the commit is appropiate or not, instead of just preaching.
Not only that, I can do that an infinite number of times, if I need to. Do you realise how of sync you are with the currrent reality?

webknjaz and eendebakpt reacted with thumbs down emojiwebknjaz reacted with confused emoji

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@ZeroIntensityZeroIntensityZeroIntensity requested changes

Assignees

No one assigned

Labels

awaiting changesdocsDocumentation in the Doc dirskip news

Projects

Status: Todo

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kovan@ZeroIntensity
[8]ページ先頭
©2009-2026 Movatter.jp