[ https://issues.apache.org/jira/browse/AIRFLOW-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048597#comment-17048597 ]
ASF subversion and git services commented on AIRFLOW-6472: ---------------------------------------------------------- Commit f85cb8709b4e27f24ccee24e90cfdc779192186d in airflow's branch refs/heads/master from Jiajie Zhong [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=f85cb87 ] [AIRFLOW-6472] Correct short and long option in cli (#7148) * [AIRFLOW-6472] Correct short and long option in cli * Make Airflow cli short options be single character only * Make Airflow cli long options be kebab-case style * Add test for airflow/bin * Update UPDATING.md > Some of the options we have are long options with single - > ---------------------------------------------------------- > > Key: AIRFLOW-6472 > URL: https://issues.apache.org/jira/browse/AIRFLOW-6472 > Project: Apache Airflow > Issue Type: Improvement > Components: cli > Affects Versions: 2.0.0, 1.10.7 > Reporter: Jarek Potiuk > Assignee: zhongjiajie > Priority: Major > > We have some "short" options that are really "long" ones: namely -int and -sd > in the run task. This is against the idea of short and long options in Unix > (and argparse follows that). The main reason to have short options is that > you can combine short options: > {{airflow task run -iAlm}} > When you have more than one letter "short" options this might become quickly > ambiguous. We do not have -s yet but if we add few more options this might > become a problem. > Also in the argparse documentation > [https://docs.python.org/2/library/argparse.html] it's mentioned that short > options should be single character only.\ > This should be fixed. > -- This message was sent by Atlassian Jira (v8.3.4#803005)