Remove black usage in prek hooks

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata

[potiuk]

We are not using black-related functionality in prek hooks any more - the only remaining hook is 'blacken-docs` - but there is no need to synchronize and upgrade black version any more for it.

Upgraded to latest black version for blacken-docs manually.

---

^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[ashb]

Makes sense

[ashb]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

[Lee-W]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

+1

[potiuk]

Somewhat relatedly, I wonder if we should switch these scripts from additional_deps to the # /// script inline metadata approach?

If prek will supports it - yes absolutely but I doubt it does - @j178 - what do you think ? Can prek support inline dependencies when creating venvs ? I think pre-commit did the optimisation that it reused the venvs if they had the same deps - but with uv doing all the heavy lifting and caching and hard-linking packages, maybe just 'per hook venvs created on the flight` is not such a bad idea ?

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 4e6fa29 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[Lee-W]

#54664

[potiuk]

Created an issue in prekj178/prek#509 to support inline script metadata