Since this is needed for 1.3 and is a quick fix: [PR #41941 ]

The reason we did the changes for 1.3 is we are going to branch soon and wanted to make sure the new style is on the backport branch to reduce the chances of autobackports failing.

I think that task is done and adding it to the other files is just to avoid new future code additions/modifications using Optional, Union, Type, Tuple, List etc in type annotations.

So just adding from __future__ import annotations to the modules that don't yet need them is unlikely to create issues with the autobackports.

This task does not therefore need to be done in time for the rc. (and if the PR was just a few additions and changes to the CI with no behavioral changes... which it should be, could be merged during the rc anyway)

STYLE add check for future annotations #41901

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions