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-118216: Don't consider dotted__future__ imports#118267

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

Merged

Conversation

thatbirdguythatuknownot
Copy link
Contributor

@thatbirdguythatuknownotthatbirdguythatuknownot commentedApr 25, 2024
edited by bedevere-appbot
Loading

Add checking for the number of dots before the module name alongside__future__ name checks inPython/future.c andPython/compile.c. Basically makes a__future__ import only be considered one when no dots are present before the module name.

@nineteendo
Copy link
Contributor

Could you also configure pre-commit?https://devguide.python.org/getting-started/setup-building/#install-pre-commit

Misc/NEWS.d/next/Core and Builtins/2024-04-25-11-48-28.gh-issue-118216.SVg700.rst:1: default role used (hint: for inline literals, use double backticks) (default-role)

Copy link
Member

@JelleZijlstraJelleZijlstra left a comment

Choose a reason for hiding this comment

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

Thanks, this looks good. Could you add an entry to the What's New for 3.13? This is arguably a change to the language semantics.

@JelleZijlstraJelleZijlstra self-assigned thisMay 2, 2024
@thatbirdguythatuknownot
Copy link
ContributorAuthor

thatbirdguythatuknownot commentedMay 2, 2024
edited
Loading

Got it.

@JelleZijlstra
Copy link
Member

@thatbirdguythatuknownot thanks! One piece of feedback: please avoid force-pushing to a PR branch, as it makes review somewhat harder. Just push a new commit and we'll squash them on merge. To update the PR branch with new commits from main, either click the "Update branch" button in GitHub or rungit merge upstream/main (or whatever your remote is called) locally.

@JelleZijlstraJelleZijlstra merged commit7c97dc8 intopython:mainMay 2, 2024
38 checks passed
@thatbirdguythatuknownot
Copy link
ContributorAuthor

Okay.

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

@JelleZijlstraJelleZijlstraJelleZijlstra approved these changes

@markshannonmarkshannonAwaiting requested review from markshannonmarkshannon is a code owner

@iritkatrieliritkatrielAwaiting requested review from iritkatrieliritkatriel is a code owner

Assignees

@JelleZijlstraJelleZijlstra

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@thatbirdguythatuknownot@nineteendo@JelleZijlstra

[8]ページ先頭

©2009-2025 Movatter.jp