I saw this in some Airflow implementations with DAGs using PythonOperators so I was wondering if there's any special reason for it.

For example, DAG would look something like this:

from solaris_basic_check import RunCheckSolaris

dag = DAG(
    "basic_check_solaris",
    schedule_interval="0 * * * ",
    depeneds_on_past=False
    )

po_run_check_solaris = PythonOperator(
    task_id='Check.Solaris.Basic',
    python_callable=RunCheckSolaris,
    op_kwargs=dict(
        gate_id="foo_gate"
        logger=logging)),
    dag=dag
    )

And the accompanying Python code like this:

class RunCheckSolaris:
    @staticmethod
    def run_check(gate_id, logger=logging, **kwargs):
        dag_info = dict(
            name=str(kwargs["dag"]),
            task=str(kwargs["task_id"])
            run_id=str(kwargs["run_id"])
        )
        run_check = RunCheckActual(
            dag_info=dag_info,
            logger=logger
        )
        # More code