Remove duplicate @staticmethod in file_task_handler.py

[KengoWada]

Apache Airflow version

3.1.8

What happened and how to reproduce it?

While reviewing the code base, I noticed that the _get_pod_namespace method is decorated with @staticmethod twice. This appears to be redundant, as applying @staticmethod once is sufficient and additional applications do not change behavior.

This does not cause a runtime error, but it introduces unnecessary duplication and may confuse readers or contributors into thinking there is a special reason for the double decoration.

Steps to reproduce

• Navigate to the file containing _get_pod_namespace
• Locate the method definition:

    @staticmethod
    @staticmethod
    def _get_pod_namespace(ti: TaskInstance | TaskInstanceHistory):
        ...

• Observe that @staticmethod is applied twice to the same method.

What you think should happen instead?

This is likely an oversight introduced during a refactor or code edit. Since applying @staticmethod multiple times does not raise an error or change behavior, the duplication would not be caught by tests or linters unless specifically checked.

As a result, the redundant decorator remained in the codebase without affecting functionality, but adds unnecessary duplication and may cause confusion for readers.

Operating System

No response

Versions of Apache Airflow Providers

No response

Deployment

Docker-Compose

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[jroachgolf84]

@KengoWada - thanks for opening up this issue! In the future (for something minor like this), just go ahead and open a PR.

[laurenhall1526-netizen]

Thanks for the quick feedback! Good point — I’ll put together a PR to remove the duplicate decorator. Appreciate you pointing me in the right direction.

…

On Mon, Mar 30, 2026, 10:38 AM Jake Roach ***@***.***> wrote: *jroachgolf84* left a comment (apache/airflow#64477) <#64477 (comment)> @KengoWada <https://github.com/KengoWada> - thanks for opening up this issue! In the future (for something minor like this), just go ahead and open a PR. — Reply to this email directly, view it on GitHub <#64477?email_source=notifications&email_token=B7IHA45B2VLZSB6RKSUBD5L4TKIHRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVGYYDCNZYHA4KM4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4156017888>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B7IHA42HERXOVLF66UDQJCT4TKIHRAVCNFSM6AAAAACXGEIXXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJWGAYTOOBYHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jroachgolf84]

@laurenhall1526-netizen (or whatever bot you are), seems like @KengoWada has already created a PR for this. No need to create a duplicate: #64479.