[
https://issues.apache.org/jira/browse/AIRFLOW-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986985#comment-16986985
]
ASF subversion and git services commented on AIRFLOW-6004:
----------------------------------------------------------
Commit a36cfe049a2c5948b24fde7a878fe19cabede5f7 in airflow's branch
refs/heads/master from Jarek Potiuk
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=a36cfe0 ]
[AIRFLOW-6004] Untangle Executors class to avoid cyclic imports (#6596)
There are cyclic imports detected seemingly randomly by pylint checks when some
of the PRs are run in CI
It was not deterministic because pylint usually uses as many processors as
many are available and it splits the list of .py files between the separate
pylint processors - depending on how the split is done, pylint check might
or might not detect it. The cycle is always detected when all files are
used.
In order to make it more deterministic, all pylint and mypy errors were
resolved
in all executors package and in dag_processor.
At the same time plugins_manager had also been moved out of the executors
and all of the operators/hooks/sensors/macros because it was also causing
cyclic dependencies and it's far easier to untangle those dependencies
in executor when we move the intialisation of all plugins to
plugins_manager.
Additionally require_serial is set in pre-commit configuration to
make sure cycle detection is deterministic.
> Untangle "Executors" class from potentially cyclic import
> ---------------------------------------------------------
>
> Key: AIRFLOW-6004
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6004
> Project: Apache Airflow
> Issue Type: Sub-task
> Components: ci
> Affects Versions: 2.0.0
> Reporter: Jarek Potiuk
> Assignee: Jarek Potiuk
> Priority: Major
>
> See the description in https://issues.apache.org/jira/browse/AIRFLOW-6003
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
