Convert airflow/hooks to __future__.annotations #26302
Conversation
boring-cyborg
bot
added
the
area:core-operators
potiuk
force-pushed
the
future_annotations_14
branch
from
562e71b
to
30625f5
Compare
| @@ -15,8 +15,10 @@ | |||
| # KIND, either express or implied. See the License for the | |||
| # specific language governing permissions and limitations | |||
| # under the License. | |||
| # fmt: off | |||
| # fmt:, off | |||
| @@ -15,8 +15,10 @@ | |||
| # KIND, either express or implied. See the License for the | |||
| # specific language governing permissions and limitations | |||
| # under the License. | |||
| # fmt: off | |||
| # fmt:, off | |||
There was a problem hiding this comment.
| # fmt:, off | |
| # fmt: off |
There was a problem hiding this comment.
Oh yeah They were small corrections I've fixed to make the PR's green (my initial replace screwed up and joined those with from __future__ import annotations.
Yeah. They actualy do (and I think the comma does not really matter) - they prevent Black from re-formatting those files . The problem with such long names of classes we have in the dict that (despite the max-line-length) it will make lines too long and they fail in flake. One of the very few cases where black is WRONG.
There was a problem hiding this comment.
I will remove those comas.
|
Closing as this one will be merged as part of #26289 #26290. See https://lists.apache.org/thread/81fr042s5d3v17v83bpo24tnrr2pp0fp for details |
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.