gh-118216: Don't consider dotted __future__ imports

[thatbirdguythatuknownot]

Add checking for the number of dots before the module name alongside __future__ name checks in Python/future.c and Python/compile.c. Basically makes a __future__ import only be considered one when no dots are present before the module name.

• Issue: __future__ imports allow dots before them #118216

[nineteendo]

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)

[JelleZijlstra]

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.

[thatbirdguythatuknownot]

Got it.

[JelleZijlstra]

@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 run git merge upstream/main (or whatever your remote is called) locally.

[thatbirdguythatuknownot]

Okay.