Bug report

Bug description:

__future__ imports don't check the amount of dots while checkingfrom-import nodes for the module name, so they are still valid even if dots are put before the module name.

>>>from .__future__import barry_as_FLUFLTraceback (most recent call last):  File "<stdin>", line 1, in <module>    from .__future__ import barry_as_FLUFLImportError: attempted relative import with no known parent package>>>1<>2True

Is this intended? Allowing dots before the module name seems improper considering__future__ is supposed to be part of the stdlib.

CPython versions tested on:

3.12, 3.13

Operating systems tested on:

Windows

Linked PRs

• gh-118216: Don't consider dotted__future__ imports #118267