Thank you for your suggestion. At first, we expected to make an SRE-friendly language and made enhancements in configuration and policy writing (try to be close to python and shell in use, and use some pythonic built-in functions such as range). However, this does bring additional learning costs to some users who are unfamiliar with python's usage. We will try to eliminate some of python's triks in the future to make the syntax and semantics of KCL clearer.